Code Reviewer Skill

Overview

Perform professional code reviews targeting local changes or remote PRs to improve correctness and maintainability. This skill is based on the popular code-reviewer skill from playbooks.com.

Purpose: Professional code reviews
Scope: Any codebase
Output: Actionable feedback

---

When to Use

• Review PRs before merging
• Review local changes before committing
• Improve code quality
• Catch bugs early
• Ensure best practices

---

Review Process

1. Gather Context

1. Identify the scope of changes
2. Understand the codebase structure
3. Check related tests
4. Look at dependency changes

2. Analyze Changes

1. Check for correctness
2. Look for edge cases
3. Verify error handling
4. Check security issues
5. Assess performance impact

3. Provide Feedback

1. Categorize issues (blocking, suggested, optional)
2. Provide specific examples
3. Suggest alternatives
4. Acknowledge good patterns

---

Review Checklist

Correctness

• Does the code do what it's supposed to?
• Are edge cases handled?
• Are there potential runtime errors?
• Does it handle null/undefined?

Security

• Input validation
• SQL injection prevention
• XSS prevention
• Authentication/authorization
• Secrets management

Performance

• Database queries optimization
• Memory usage
• Algorithmic complexity
• Caching opportunities

Maintainability

• Code organization
• Naming conventions
• Comment quality
• Function complexity
• Test coverage

Best Practices

• Language idioms
• Framework conventions
• Design patterns
• Error handling
• Logging

---

Output Format

Summary

## Code Review Summary

### Overall
- **Verdict**: [Approve / Request Changes / Approve with Comments]
- **Issues Found**: X blocking, Y suggested, Z optional

### Files Changed
- [file1.ts] - X changes
- [file2.js] - Y changes

Detailed Feedback

## Issues

### 🔴 Blocking (Must Fix)
1. [File:Line] - Issue description
   - Why it's a problem
   - Suggested fix

### 🟡 Suggested (Recommended)
1. [File:Line] - Suggestion
   - Rationale
   - Example

### 🟢 Optional (Nice to Have)
1. [File:Line] - Optional improvement

---

Integration

With GitHub

1. Run: gh pr view <number> --json body
2. Get diff: gh pr diff <number>
3. Review and comment

With Git

1. Get changes: git diff HEAD~1
2. Analyze code
3. Generate feedback

---

Best Practices

Do's

✅ Be specific and actionable
✅ Provide code examples
✅ Acknowledge good patterns
✅ Consider the author's intent
✅ Focus on important issues

Don'ts

❌ Don't be nitpicky
❌ Don't rewrite code without explaining
❌ Don't ignore context
❌ Don't forget security

---

Version History

• v1.0 (2026-02-27) - Initial creation
  • Based on playbooks.com code-reviewer

---

Related Skills

• frontend-design - Design skills
• testing - Test coverage
• skill-performance-monitor - Track improvements