Skip to content

Code Review skill

When reviewing a change, work through these in order and stop at the first blocking issue:

  1. Correctness — off-by-one errors, None/null handling, and every error path (not just the happy path).
  2. Security — injection, path traversal, and secrets reaching logs.
  3. Clarity — naming, dead code, and missing tests for the new behavior.

Report findings as a short, prioritized list; lead with anything blocking.