Code Review

Use this skill to review changed code with a senior-engineer stance: find real bugs and risks introduced by the change, avoid noise, and lead with actionable findings.

Scope

Review only the changed behavior unless the user explicitly asks for a broader audit. Do not treat pre-existing issues as findings unless the change makes them newly reachable or worse.

For GitHub PRs, require gh to be installed and authenticated. Use gh for PR metadata, PR diffs, previous PR comments, and posting comments when requested. Use git for local diffs, branch history, blame, and full commit SHAs.

Do not run builds, typechecks, linters, or test suites as part of review unless the user asks. CI should catch compiler, formatter, import, and basic lint failures.