After an agent implements something, you need to review it before it becomes part of your codebase. Review (Mod+6) is the git diff viewer where you examine changes and decide whether they move forward.
Press Mod+6 to open it.
What you see
The Review surface shows your uncommitted changes. The file list appears on the left (or as an accordion, depending on your layout). Select a file to see its diff in the main pane.
Layout modes
- Stacked — files appear as an accordion list. Each file can be expanded or collapsed. Good for reviewing many small changes.
- Sidebar — file list on the left, diff on the right. Good for reviewing large files.
Toggle between them using the layout button in the header.
Diff views
- Split — old version on the left, new version on the right. Good for seeing what changed line by line.
- Unified — changes appear inline with context. Good for getting a quick overview.
File filters
Filter by status: Pending (not yet reviewed), Accepted (you approved), Rejected (you declined). This helps when reviewing large changes over multiple sessions.
What you can do
Accept a file — marks it as approved. The change is staged for commit.
Reject a file — marks it as declined. The agent will need to revise it.
Accept all / Reject all — bulk actions for when you trust or distrust the entire changeset.
Undo last step — if you accepted something by mistake, undo it.
AI review — asks kreviewer to look at the changes and flag potential issues. This is a second opinion, not a replacement for your own review.
Review summary — generates a high-level summary of what changed across all files.
Working with agents
After reviewing, you have two options:
- Accept the changes — they are staged and ready to commit
- Request revisions — tell the agent what needs to change, and it produces a new version
If you request revisions, be specific. "The auth handler doesn't check for expired tokens" is more useful than "this looks wrong."
A typical review session
- Press Mod+6 to open Review
- Switch to sidebar layout if there are many files
- Start with the first file. Read the diff. Check that it does what the story asked for.
- Look for: correct files touched, tests added, no unrelated changes
- Accept files that look right, reject ones that don't
- For rejected files, add a comment explaining why
- When done, either commit the accepted changes or ask the agent to revise the rejected ones
Related pages
- Fix a bug — review is the final step in the bug fix flow
- Plan a feature — review happens after implementation
- Agents — kreviewer for automated review