Code Review Skill

Use this skill to review code thoroughly and consistently. Adapt the depth to the scope: a single file gets a focused review, a PR gets a diff-based review, a whole codebase gets a multi-pass audit.

Step 1 — Establish scope

Before reviewing anything, figure out what you're reviewing:

• PR / branch: get the diff. git diff <base>...HEAD or gh pr diff <number>. Confirm the correct base branch — don't assume main.
• File or folder: read the full file(s), plus the immediate callers of any exported symbol.
• Whole codebase: map the structure first (package.json, configs, folder layout, entry points), then plan passes by area.

Read full files, not just hunks. Read callers of changed functions. Context prevents wrong feedback.

If scope is unclear, ask before reviewing.

Step 2 — State assumed intent

Read the PR description, commit messages, or ask the user what the change is for. State your understanding of the intent at the top of the review. Review against that intent.