05 - Changes and Review#

Helmor makes agent edits visible at every step. The goal: review is part of the agent workflow, not a separate cleanup phase.

What Helmor shows#

After an agent session runs, you see:

Session summary — what the agent attempted and the tools it used.
Changed files — a file list with inline diffs, additions, and deletions.
Workspace state — the current branch, uncommitted changes, and target branch comparison.

Everything is accessible from the workspace view without switching to a terminal or external diff tool.

Read the session output — confirm the agent understood the task.
Inspect the diff — open changed files and verify each edit matches the original request.
Run checks — execute tests, linting, or builds from your terminal or CI. Helmor does not run these automatically.
Decide next action:
- ✅ Commit — stage and commit the changes locally.
- 🔁 Continue — send a follow-up prompt to refine the work.
- ❌ Discard — reset the workspace to its pre-session state.

Red flag	Why it matters
Unrelated refactors	Agents sometimes "improve" code beyond the request.
Formatting churn	Large diffs that change whitespace obscure real edits.
Missing tests	New behavior without coverage is risky to ship.
Symptom-level fixes	Agents may patch a surface bug without addressing the root cause.

A change is ready to ship when:

The diff is understandable — a teammate could review it without context beyond the session history.
Expected checks pass — tests, types, lint.
The session explains the work clearly enough to serve as commit context.

Helmor makes agent edits visible at every step. The goal: review is part of the agent workflow, not a separate cleanup phase.

After an agent session runs, you see:

Session summary — what the agent attempted and the tools it used.
Changed files — a file list with inline diffs, additions, and deletions.
Workspace state — the current branch, uncommitted changes, and target branch comparison.

Everything is accessible from the workspace view without switching to a terminal or external diff tool.

Read the session output — confirm the agent understood the task.
Inspect the diff — open changed files and verify each edit matches the original request.
Run checks — execute tests, linting, or builds from your terminal or CI. Helmor does not run these automatically.
Decide next action:
- ✅ Commit — stage and commit the changes locally.
- 🔁 Continue — send a follow-up prompt to refine the work.
- ❌ Discard — reset the workspace to its pre-session state.

Red flag	Why it matters
Unrelated refactors	Agents sometimes "improve" code beyond the request.
Formatting churn	Large diffs that change whitespace obscure real edits.
Missing tests	New behavior without coverage is risky to ship.
Symptom-level fixes	Agents may patch a surface bug without addressing the root cause.

A change is ready to ship when:

The diff is understandable — a teammate could review it without context beyond the session history.
Expected checks pass — tests, types, lint.
The session explains the work clearly enough to serve as commit context.