code-review

Review local code changes. Choose the reviewer based on where the implementation context lives:

• You implemented the changes in this session (or took part in the design/implementation conversation): dispatch an isolated sub-agent — a fresh agent with no knowledge of this session's implementation decisions. This eliminates the bias of reviewing your own work.
• Fresh session, review-only request (the user opened this session just to have you review a diff/PR you had no part in): you already ARE the unbiased fresh pair of eyes — review the code yourself, following the same template in code-reviewer.md. Spawning a sub-agent here only adds latency and a context hand-off with zero isolation benefit. Skip step 2 and produce the review report directly.

Process

1. Gather context for the review

Collect everything the reviewer needs:

# What changed
git log --oneline main..HEAD
git diff main...HEAD
git diff
git diff --cached

Also identify:

• Tech design doc path (if one exists in conversation context or commit messages)
• Which services/modules are touched
• Test files added or modified

2. Dispatch the sub-agent (only when you wrote the code)

Call the sub_agent tool with subagent_type: "code-review" — a read-only reviewer that starts with zero context. Pass it the diff range, file list, and tech design reference in the prompt — but NOT your implementation reasoning or conversation history.

If you need to review multiple independent changes (e.g., several PRs), dispatch one sub-agent per change in the same round — they run in parallel. When a dispatch comes back as a handle rather than a result, end your turn and use the completion notification when it arrives. Do not poll sub_agent_status while waiting; use it only if you suspect an agent is stuck or need to list running agents.

The sub-agent prompt should follow the template in code-reviewer.md.

Fill in:

• {DESCRIPTION} — brief summary of what these changes do
• {TECH_DESIGN_PATH} — path to tech design doc (or "none")
• {BASE_SHA} / {HEAD_SHA} — git range
• {DIFF_STAT} — output of git diff --stat