GitHub Code Review
Use this skill when the user asks for a PR review or wants actionable findings from a GitHub diff.
Review Order
- Read PR metadata and changed files.
- Focus first on correctness, regressions, missing tests, and broken assumptions.
- Keep findings concise, severity-ordered, and file-grounded.
- Only after findings should you summarize the broader change.
Guardrails
- Avoid style-only noise unless it hides a real defect.
- If there are no findings, say so explicitly and mention residual risk.