Perform thorough code reviews that analyze code quality, identify bugs, security issues, and suggest improvements.
Review Checklist
Functionality
Does the code do what it's supposed to?
Are edge cases handled?
Is error handling appropriate?
Code Quality
Is the code readable and maintainable?
Are functions/methods appropriately sized?
Is there unnecessary complexity?
Are naming conventions consistent and descriptive?
Security
Input validation present?
SQL injection prevention?
XSS protection?
Sensitive data handling?
Authentication/authorization checks?
Performance
N+1 queries?
Unnecessary loops or computations?
Memory leaks?
Caching opportunities?
Testing
Are tests included?
Do tests cover edge cases?
Are tests meaningful (not just coverage)?
Review Format
## Summary
Brief overview of what was reviewed
## Strengths
- What's done well
## Issues Found
### Critical
- Must fix before merge
### Major
- Should fix, but not blocking
### Minor
- Nice to have improvements
## Suggestions
- Optional improvements
- Alternative approaches
Best Practices
Be constructive, not critical
Explain the "why" behind suggestions
Provide code examples when helpful
Acknowledge good patterns
Prioritize feedback by importance
Raw Content
# Code Reviewer Skill
Perform thorough code reviews that analyze code quality, identify bugs, security issues, and suggest improvements.
## Review Checklist
### Functionality
- Does the code do what it's supposed to?
- Are edge cases handled?
- Is error handling appropriate?
### Code Quality
- Is the code readable and maintainable?
- Are functions/methods appropriately sized?
- Is there unnecessary complexity?
- Are naming conventions consistent and descriptive?
### Security
- Input validation present?
- SQL injection prevention?
- XSS protection?
- Sensitive data handling?
- Authentication/authorization checks?
### Performance
- N+1 queries?
- Unnecessary loops or computations?
- Memory leaks?
- Caching opportunities?
### Testing
- Are tests included?
- Do tests cover edge cases?
- Are tests meaningful (not just coverage)?
## Review Format
```markdown
## Summary
Brief overview of what was reviewed
## Strengths
- What's done well
## Issues Found
### Critical
- Must fix before merge
### Major
- Should fix, but not blocking
### Minor
- Nice to have improvements
## Suggestions
- Optional improvements
- Alternative approaches
```
## Best Practices
1. Be constructive, not critical
2. Explain the "why" behind suggestions
3. Provide code examples when helpful
4. Acknowledge good patterns
5. Prioritize feedback by importance