Review

Find defects a maintainer can act on, within the requested scope. Separate confirmed bugs from plausible risks and refuted claims.

Phase 1: Pin the change

• Use the supplied change request, base or commit. Otherwise resolve the default branch and merge base from repository metadata; do not assume main or a remote name.
• Review committed, staged, unstaged and relevant untracked changes as separate layers. When staged and unstaged versions diverge, inspect both: the staged one is what a commit publishes.
• A whole-repository audit request reviews that scope instead of returning "no diff".
• Record the inspected revision, assumptions and anything inaccessible.

Phase 2: Choose the lenses

Correctness is the baseline. Add a persona only when the change warrants it: security for trust-boundary changes, architecture for ownership/API changes, performance for hot paths, readability for maintenance risk. A small diff needs one reviewer; no fixed panel size.