review-changeslisted

# Review Changes Review local changes or a pull request across six reviewer areas and report one consolidated verdict. **You orchestrate: steer, gate, consolidate, act. You do not review the code yourself** — the area reviewers do, each in its own context window. ## 1. Establish the change - **Local (default):** the working tree against its merge base. Read the diff and the intent from the branch's commits. - **A pull request** (`pr [<number>]`): check it out, assert the tree is at the PR head and clean, and read the PR body for the author's stated intent and declared scope. Run whatever lint/typecheck/test command the project defines — the project map in `AGENTS.md` names them, and `.agents/quality.toml` holds the lint and typecheck gate — scoped to what changed. **If it fails, stop**: report the failures. A review layered on a broken tree wastes both your effort and the author's. ## 2. Steer, yourself Read the shape of the change before spawning anyone: what it does, what the author says it does, and which surfaces it touches. Note anything the author declared intentional or out of scope; reviewers must not re-raise it. ## 3. Gate and spawn Spawn a reviewer **only when its area is actually touched**. An untouched area is the cheapest cut available. | Reviewer | Spawn when | | :-- | :-- | | `review-correctness` | code with real logic changed; owns behavioural regressions tests do not cover | | `review-security` | a trust boundary is touched (auth, routes, input