Review

Code Review Skill

Perform a comprehensive code review on the specified files, directory, or recent changes.

Usage

/review                     # Review all uncommitted changes
/review src/api/            # Review all files in a directory
/review src/auth/login.ts   # Review a specific file
/review --last-commit       # Review the last commit

Steps

1. Determine what to review

• If a path is provided, review those files
• If --last-commit flag, review git diff HEAD~1
• If no arguments, review git diff (all uncommitted changes)

1. Read and analyze the code

For each file, check:

### Correctness

• Logic errors or bugs
• Off-by-one errors
• Null/undefined handling
• Race conditions
• Edge cases not handled

### Security

• SQL injection vulnerabilities
• XSS vulnerabilities
• Hardcoded secrets or credentials
• Improper input validation
• Authentication/authorization issues

### Performance

• N+1 query problems
• Unnecessary re-renders (React)
• Missing indexes (if DB queries visible)
• Memory leaks
• Expensive operations in loops

### Code Quality

• Naming clarity
• Function length and complexity
• Code duplication
• Proper error handling
• Type safety (TypeScript)

### Testing

• Are new features tested?
• Are edge cases covered?
• Are tests meaningful (not just checking happy path)?

1. Generate the review

Output a structured review with:

• Summary (1-2 sentences)
• Findings grouped by severity:
• Critical — must fix before merge
• Warning — should fix, potential issues
• Suggestion — nice to have improvements
• Praise — good patterns worth noting
• Each finding should include:
• File and line reference
• Description of the issue
• Suggested fix (with code if applicable)

Output Format

## Code Review Summary
[Brief overview]

### Critical (X issues)
- **[file:line]** — [description]
  Suggested fix: [solution]

### Warnings (X issues)
- **[file:line]** — [description]

### Suggestions (X items)
- **[file:line]** — [description]

### Highlights
- **[file:line]** — [what's good about it]

Rules

• Be constructive, not harsh
• Provide actionable suggestions with code examples
• Don't nitpick formatting if there's a formatter configured
• Focus on logic and architecture over style
• Always mention good patterns too — reviews shouldn't be only negative

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: CanArslanDev
• Source: CanArslanDev/claude-code-setup
• License: MIT

Install and usage instructions live in the source repository linked above.