review-prlisted

# Review a pull request Read the [shared review contract](../../contracts/review-contract.md) before executing this workflow. Its evidence, candidate ledger, execution and verdict rules apply throughout. Run the four-stage swarm described below. Use the host model and native delegation tools; see the runtime section below. Read-only — never merge, push, or edit. ## Inputs - A PR number/URL, or "the current branch". If ambiguous, ask which PR. ## Stage 1 — Skip-gate (inline, cheap) ```bash gh pr view <PR> --json number,title,state,isDraft,body,additions,deletions,baseRefName,headRefName,headRefOid,url ``` Stop early (and say why) if the PR is closed/merged, a draft the user didn't ask to review, or a trivial no-logic change (typo, formatting). Don't summon a swarm for nothing. ## Stage 2 — Collect context ```bash gh pr diff <PR> # the change under review gh pr view <PR> --json files # files touched gh pr view <PR> --comments # existing review comments (dedup against them) ``` Diff a local branch instead with `git diff --merge-base origin/HEAD` (three-dot = only what the branch introduces). Read the surrounding code, not just the hunks. Note the stated intent (PR body / linked issue) — every change should trace to it. ## Stage 3 — Fan out the swarm (parallel, single message, host-configured models) Dispatch one subagent per relevant lens. **Scale to the diff:** a tiny fix → `correctness` + `security`; a large/risky change → all o