Daboggieman Code Review Skill
Objective
Find meaningful problems before code reaches production.
Review Order
Review in this order:
- Correctness
- Security
- Data integrity
- Error handling
- Regression risk
- Performance
- Maintainability
- Style
Correctness takes priority over stylistic preferences.
Process
- Inspect git status.
- Inspect the complete diff.
- Understand the surrounding implementation.
- Trace affected execution paths.
- Check edge cases.
- Check error handling.
- Check security implications.
- Check compatibility with existing behavior.
- Run relevant tests.
Findings
For every real finding provide:
- Severity
- Location
- Problem
- Why it matters
- Concrete fix
Do not report purely stylistic preferences as bugs.
Do not invent hypothetical problems without a plausible execution path.
Severity
Use:
- CRITICAL — severe security, data-loss, or system-breaking issue
- HIGH — major functional or security issue
- MEDIUM — meaningful defect or regression risk
- LOW — minor issue worth addressing
Do not assign severity without explaining the impact.
Final Review
After reviewing, distinguish:
- Confirmed issues
- Potential risks
- Areas checked without findings
Never declare code safe merely because no obvious issue was found.