security-review

Review the change adversarially — assume the diff is hostile until proven safe. Report only findings you can tie to a concrete failure scenario; do not pad with generic advice.

Scope the diff

1. Establish the base: git diff <base>...HEAD for a branch, gh pr diff <n> for a PR, or git diff for the working tree. Read enough surrounding context to judge each hunk — never review a hunk in isolation.
2. If the change is large, fan out: one reviewer per trust boundary (auth, input parsing, secrets, CI/exec, file I/O), then dedupe. A single pass misses cross-cutting issues.

What to hunt for