Adversarial code review

Look for defects that survive an ordinary review. Treat the implementation's assumptions as claims to verify, while keeping every finding tied to evidence.

Establish the review boundary

1. Identify the exact diff, branch, pull request head, or files under review.
2. Read the surrounding code needed to understand data flow and invariants.
3. Check repository instructions and the tests that define expected behavior.
4. Compare the change with its stated purpose. Trace the scenario and configuration from the issue, discussion, or accepted design it addresses through the real code, and treat each claim in the description and changeset as something to verify.
5. Separate defects introduced by the reviewed change from unrelated observations. Report an out-of-scope issue only when it materially affects the change's safety.

Do not modify code, post a review, or expand the review target unless the user asks.

Hunt for failures

Choose the checks that fit the change instead of mechanically applying every category.