Review

Review a whole change and return one report of its findings to whoever ran the review. correctness-review and test-review run on every change; each other area runs only when the diff touches it. Change nothing and commit nothing, in any mode: whoever ran the review fixes what it finds.

Two modes: Self (no argument, or a commit range) — the current branch's diff against the branch it lands on, or the given range, or the diff file the brief names; PR (URL or number) — someone else's PR. Code already on the default branch with no change to bound it is audit.

Scope

Review only the diff, but read enough surrounding code and docs to understand conventions and boundaries.

Do not duplicate the same issue across areas. A finding backed by the repo's own docs, contracts or nearby code belongs to Architecture or Maintainability; one that holds regardless of the repo belongs to Design. Where a Design rule and a documented repo convention conflict, the convention wins: Design raises nothing, and Maintainability reports only a departure from the convention.

Change sizing

Before reviewing, check the diff size:

• ~100 lines: good, reviewable in one pass.
• ~300 lines: fine when it is one logical change.
• ~1000 lines: too large — ask the author to split before reviewing.