review

/review                              # review current branch vs main
/review my-feature-branch            # review a specific branch vs main

Spawns dedicated Breaker (correctness) and API Analyst (compatibility/conventions) sub-agents in parallel while the orchestrator performs the Inspector pass (architecture, tests, performance, security). Depth is user-selected.

Optimize for high-confidence, concise findings. Silence is better than speculation.

Input

Target: $ARGUMENTS

Parse $ARGUMENTS:

1. Review target (positional argument):
   • Non-empty text (e.g., my-feature-branch) -> diff that branch vs main
   • Empty -> diff current branch vs main

Step 1: Confirm Mode

Before doing anything, ask the user:

I can run a code review on your branch. Pick a depth (fastest to slowest):

1. Skip — skip the review
2. Quick — single-pass by orchestrator, all areas, no sub-agents
3. Standard — full swarm: Breaker + API Analyst sub-agents + Inspector
4. Deep — Standard + reads full changed files (not just diffs) for deeper analysis

Wait for the user's response. If they say skip, stop here.

<required> Immediately after the user picks a mode, create one task per applicable step using TaskCreate — before doing any other work. Mark each task in_progress when you start it and completed when you finish.

Tasks to create by mode:

• Quick: Gather changes -> Read diffs -> Perform single-pass review -> De-duplicate and classify -> Report
• Standard: Gather changes -> Read diffs -> Detect API surface changes -> Extract sections for sub-agents -> Perform review (spawn Breaker + API Analyst, run Inspector) -> De-duplicate and classify -> Report
• Deep: Gather changes -> Read diffs and full files -> Detect API surface changes -> Extract sections for sub-agents -> Perform review (spawn Breaker + API Analyst, run Inspector) -> De-duplicate and classify -> Report </required>

Step 2: Setup & Gather Changes

git fetch origin main && git log origin/main..HEAD --oneline && git diff --stat origin/main...HEAD

If a branch name was provided as argument, replace HEAD with origin/<branch-name> and add it to the fetch:

git fetch origin main <branch-name> && git log origin/main..origin/<branch-name> --oneline && git diff --stat origin/main...origin/<branch-name>

If on main and no branch name was provided, ask the user which branch to review.

Store the commit log, file list from --stat, and total $LINES_CHANGED.

Empty diff gate: Zero changed files -> report "No changes to review" and stop.

Size gate: >10,000 lines changed -> ask user to narrow scope before proceeding.

Step 3: Read Diffs and Source Files

Exclude non-reviewable files from the file list: type declarations (.d.ts), lockfiles (pnpm-lock.yaml, package-lock.json), images, fonts, binaries, .map files, and generated API report files (*.api.md).

Read per-file diffs in batches (~50 files or ~500 changed lines per batch, whichever is smaller):

git diff origin/main...HEAD -- <file1> <file2> ...

For named branches, use origin/main...origin/<branch>.

Standard mode: selective full-file reads

After reading diffs, identify files where fuller context is needed — typically where the change touches a function that references shared state, calls other functions in the same file, or has fragmented hunks. Read those files in one batch using the Read tool.

Deep mode: full-file reads for all changed files

Read every changed file in full (the version on the review branch). Use git show HEAD:<file> or git show origin/<branch>:<file> as appropriate.

Shared plumbing trap

If a change threads a new prop, callback, flag, or data field through a shared component or helper, read every changed call site and adjacent wrapper that accepts or forwards it.

…