02 - Review Agent Changes#
After an agent session completes, review the results before committing. Helmor surfaces everything you need to decide whether the work is ready to ship.
What Helmor shows you#
- Session summary — the agent's final output and reasoning.
- Changed files — a file list with inline diffs (additions, deletions, modifications).
- Tool call log — every file read, edit, and command the agent executed.
- Workspace state — current branch, uncommitted changes, and comparison against the target branch.
All of this is accessible from the workspace view without switching tools.
Review checklist#
Work through these before committing:
- Does the diff match the task? — Every changed line should trace back to the original prompt.
- Are there unrelated edits? — Agents sometimes refactor beyond scope or apply formatting changes. Remove or reject these.
- Are tests included? — New behavior should have coverage. If the agent skipped tests, continue the session and ask for them.
- Does the build pass? — Run your project's test and lint commands locally.
- Is the change small enough to understand? — If the diff is too large, consider splitting the task.
Red flags#
| Signal | Risk |
|---|---|
| Large formatting-only diffs | Obscures real changes; makes future review harder. |
| Unrelated refactors | Scope creep — agent "improved" something you didn't ask for. |
| Missing error handling | Agent solved the happy path but ignored edge cases. |
| Symptom-level fix | The root cause may still be present. |
Actions after review#
- Commit — stage and commit the changes.
- Continue — send a follow-up prompt to refine the result.
- Discard — reset the workspace to its pre-session state.
Related#
- Commit and Ship Work — what happens after you approve.
- Continue an Existing Session — iterate on the agent's output.