Code Review

Code review is a judgment surface, not a generic style pass. Optimize for the highest-signal findings: correctness bugs, behavioral regressions, trust-boundary mistakes, performance risks, and missing verification.

When to use this skill

• Review a pull request, diff, merge request, or patch stack before merge
• Decide whether a change should be approved, blocked, or sent back for fixes
• Identify the most important bugs, regressions, or missing tests in a change
• Turn vague "please review this" requests into a risk-ranked findings list
• Check whether the stated intent of a change matches what the diff actually does

Prefer a neighboring skill when the main job is not reviewing a concrete code change: