code-review
When to use
Use this skill when asked to review code changes, pull requests, or files for quality issues.
Process
- Read the changed files completely before commenting
- Check for correctness bugs first
- Check for security issues (injection, auth bypass, data exposure)
- Check for maintainability (naming, structure, complexity)
- Provide specific, actionable feedback with line references
Principles
- Be specific: "line 42: this SQL query is vulnerable to injection" not "watch out for SQL injection"
- Suggest fixes, don't just point out problems
- Acknowledge good patterns when you see them
- Prioritize: blocking issues first, then improvements, then style