Skip to Content
DocsReferenceCLI CommandsFeature Commandsfeature-code-review

Synopsis

aigon feature-code-review <ID>

Shortcuts

  • /afr (slash command) · aigon afr (CLI)

Description

feature-code-review assigns a reviewer agent to inspect and fix a feature’s implementation. Unlike a traditional read-only review, this is a write-capable review pass — the reviewing agent reads the diff, identifies concrete issues, and patches them directly in the feature worktree with fix(review): ... commits. A findings-only report is appropriate only when issues require architectural decisions or missing context that the reviewer cannot resolve alone.

For the best results, use a different model than the implementer. Model diversity catches different classes of bugs.

The reviewer checks: correctness against acceptance criteria, out-of-scope file deletions, test coverage, and code quality — in that priority order.

What it does

  1. Fetches the full diff (git diff main..feature-<ID>-*) and the implementation log
  2. Runs aigon agent-status reviewing to signal the dashboard
  3. Checks for out-of-scope deletions (files not related to the spec)
  4. Reviews correctness against the spec’s acceptance criteria
  5. Patches issues directly in the feature worktree with fix(review): ... commits
  6. Signals review-complete when done

Dashboard card after review

Once the reviewer signals completion, the card shows a verdict badge below the reviewer’s status line. There are two outcomes:

Dashboard card showing a completed code review with the green Approved verdict badge

✓ Approved — reviewer found no issues. The feature is ready to close as-is.

⚠ Revision requested — issues found. Use Address review from the ⋯ menu to start a revision pass.

The eye icon (👁) next to “Review” lets you peek at the reviewer’s session to read the full findings before deciding whether to revise or close.

Examples

# Run a code review on feature 42
aigon feature-code-review 42
 
# From within an agent session (use a different model than the implementer)
/aigon:feature-code-review 42

When to use

Use feature-code-review in the solo Drive mode workflow — after the implementer submits, before closing. In Fleet mode, use feature-eval to compare implementations instead.

For the automated equivalent (AutoConductor runs review for you), see feature-autonomous-start --review-agent=<agent>.

Last updated on
feature-evalfeature-code-revise