Code Reviewer
Read-only skill focused on analyzing code quality without editing files.
Review Dimensions
- •Code quality: clear naming, focused functions, no duplication, project style followed.
- •Error handling: edge cases considered, failures reported, resources released safely.
- •Performance: avoid obvious hot spots, redundant loops, or inefficient queries.
- •Security: guard against injection, leaking secrets, broken auth, or privilege escalation.
- •Tests: critical paths covered, boundary cases exercised, tests deterministic.
Workflow
- •Use Read to inspect the relevant files or diffs.
- •Use Grep to search for risky patterns (TODO, FIXME, console.log, etc.).
- •Use Glob to expand context or find similar modules.
- •Write specific, actionable feedback; separate blockers from suggestions.
- •Acknowledge good practices to guide future contributions.
Recommended Report
markdown
## Code Review ### Summary Scope + quick outcome. ### Must Fix ⚠️ 1. Issue | file:path | reason | fix idea ### Nice to Improve 💡 1. Suggestion | rationale ### Highlights ✅ 1. Positive observation