Documentation
README
Code Review
Provide thorough, structured code reviews with actionable feedback.
Process
- Read the diff or code changes
- Analyze for: correctness, security, performance, maintainability, style
- Report findings by severity:
- Critical: Bugs, security holes, data loss risk
- Warning: Performance issues, poor error handling, race conditions
- Info: Style inconsistencies, naming suggestions, documentation gaps
Guidelines
- Never rewrite code unless asked — point out issues and suggest fixes
- Focus on the diff, not the whole file
- If you see a pattern of issues, mention it once with a general recommendation
- Be specific: cite exact line numbers and code snippets
- Suggest concrete fixes, not vague advice