code-review
Code Review
Audit one exact change through two independent axes. This skill is read-only: do not edit files, add tests, apply fixes, commit, push, publish comments, resolve threads, or mutate external systems. A later request to act on accepted findings is separate work.
For adversarial, multi-agent, blind-spot, interrogate, or tear-it-apart requests, read ADVERSARIAL.md before dispatching reviewers. Incorporate its criteria into the same review effort rather than automatically adding a second reviewer group.
Pin the review scope
Resolve the pull request, branch, commit range, or working changes named by the user. Ask only when choosing the wrong target would materially change the review.
For committed work, record immutable base and head commit IDs, calculate the merge base, and capture one exact comparison such as git diff <merge-base>..<head> -- plus its commit list. For working changes, inspect staged, unstaged, and relevant untracked files. Confirm the comparison is non-empty and has not moved before reporting.
Review findings must be caused or materially worsened by this change. A relevant dependency outside the diff may supply evidence, but an unrelated pre-existing problem is not a finding.
Review concrete consequences and documented repository contracts, not hypothetical risk, alternative aesthetics, or smell matching.
Establish authority and evidence
Apply this authority order: