Review Phase

Resolve the diff, fan out parallel read-only reviewers — each in its own subagent so a11y and security reasoning don't bleed into each other — and consolidate into one severity-ranked verdict. Findings two reviewers reach independently are the highest signal — surface that convergence.

Reviewers come from two sources: audit skills selected by file type in the diff (a11y-audit, i18n, perf-audit, deps-audit, harden, safe-repo) and agent lenses applied to the whole diff (correctness, standards, spec conformance, test effectiveness, type safety, architecture friction). The quality-bar check is a script you run inline.

Workflow

1. Resolve the diff

PR number → gh pr view + gh pr diff (fails → current-branch diff, warn). Branch → git diff <base>...<branch>. Nothing → git merge-base HEAD main (fall back master, origin/HEAD, then HEAD~10 with a warning), then git diff <base>...HEAD. Empty diff → "Nothing to review", stop. State the scope: "Reviewing branch X vs main — 6 files, 224 insertions."

2. Select reviewers

Always: correctness (code-review), standards, sensitive data (safe-repo --diff <base>), test effectiveness, quality bar. Spec whenever this work has one, read from the tracker (.specs/issue-tracker.md, else the local default) by branch slug or the ticket refs in commits. Add the rest from the diff. An explicit count in $ARGUMENTS (2–8) caps the subagents; drop diff-selected ones first. Never spawn visual-review in UI mode: it needs a dev server the user owns.