aigon-feature-code-review

aigon-feature-code-review

Perform a code review on another agent's implementation, making targeted fixes where needed. Use a different model than the implementer for best results.

You are doing a write-capable review pass, not a read-only review report. Ignore any default "code review means findings-only" behavior for this task; this command is specifically a review-with-fixes workflow.

Your default action is:

1. identify a concrete issue
2. patch it in the feature worktree
3. commit it with fix(review): ...
4. leave only residual issues in notes

Do not stop at describing a fix if you can safely make it yourself. A findings-only review is valid only when:

• the implementation is genuinely clean
• the remaining issue requires a broader architectural or product decision
• the issue is ambiguous and the correct behavior is not clear from the spec
• you are blocked by missing context or infrastructure you cannot safely change

Argument Resolution

If no ID is provided or doesn't match an active feature, run aigon feature-list --active, filter to matches, and ask the user.

Step 1: Gather all context (one tool call)

Run this entire block in a single shell execution — do not split it up. It fetches branch info, the full diff, and the implementation log in one shot so you can review immediately without extra round-trips.

You MUST commit review changes to the FEATURE WORKTREE, never to main.

BRANCH=$(git branch --show-current)
FEATURE_BRANCH=$(git branch --list 'feature-<name>-*' | head -1 | tr -d ' *')
WORKTREE=$(git worktree list | grep "feature-<name>" | awk '{print $1}')
echo "=== WORKSPACE ==="
echo "Current: $BRANCH  Feature: $FEATURE_BRANCH  Worktree: $WORKTREE"
echo "=== DIFF ==="
git diff "main...${FEATURE_BRANCH:-HEAD}"
echo "=== IMPLEMENTATION LOG ==="
cat docs/specs/features/logs/feature-<name>-*-log.md 2>/dev/null || echo "(no log found)"
aigon agent-status reviewing

The spec body was printed inline by the launching CLI — use that copy for acceptance criteria.