code-review
Automated code review against project conventions (CLAUDE.md) and best practices
When & Why to Use This Skill
This Claude skill automates the code review process by analyzing git diffs, pull requests, and specific files against project-specific conventions (CLAUDE.md) and industry best practices. It delivers prioritized, actionable feedback—ranging from critical security vulnerabilities to code style—ensuring high-quality commits and consistent architectural standards across the development lifecycle.
Use Cases
- Pre-commit Validation: Reviewing staged changes to identify logic errors or security risks before they are committed to the repository.
- Pull Request Auditing: Automatically analyzing specific PRs to provide comprehensive feedback on performance, maintainability, and adherence to project rules.
- Project Convention Enforcement: Ensuring all new code strictly follows the architectural patterns and naming conventions defined in the project's CLAUDE.md file.
- Deep File Analysis: Performing an in-depth review of complex legacy files to identify technical debt, N+1 queries, or potential memory leaks.
- Branch Comparison: Comparing feature branches against the main branch to evaluate the overall impact and quality of a large set of changes.
| name | code-review |
|---|---|
| description | Automated code review against project conventions (CLAUDE.md) and best practices |
| version | 1.0.0 |
| compatibility | Requires git CLI |
| category | development |
| requires | git |
| platforms | claude-code,cursor,vscode,github-copilot |
Core Philosophy
Code review should be:
- Convention-aware - Follows project-specific rules from CLAUDE.md
- Actionable - Every comment includes a specific fix
- Prioritized - Critical issues first, style last
- Contextual - Understands the change's purpose
Review Categories (Priority Order)
- 🔴 Critical - Security vulnerabilities, data loss risks, crashes
- 🟠 Bugs - Logic errors, edge cases, race conditions
- 🟡 Performance - N+1 queries, memory leaks, inefficient algorithms
- 🔵 Maintainability - Code clarity, naming, documentation
- ⚪ Style - Formatting, conventions, nitpicks
Key Rules
- NEVER approve code you haven't read
- ALWAYS read CLAUDE.md first if it exists
- Spawn fresh context for large reviews to avoid bias
- Be specific - line numbers, code snippets, fixes
- Stay focused - review what changed, not the whole file
Code Review
What would you like to review?
- Current diff - Review uncommitted changes (
git diff) - Staged changes - Review staged changes (
git diff --staged) - PR by number - Review a specific pull request
- Specific file - Review a single file in depth
- Branch comparison - Compare two branches
Enter your choice or describe what you want reviewed:
| Response Pattern | Workflow |
|---|---|
| "1", "current", "diff", "changes" | workflows/review-diff.md |
| "2", "staged" | workflows/review-staged.md |
| "3", "pr", "#\d+", "pull request" | workflows/review-pr.md |
| "4", "file", specific filepath | workflows/review-file.md |
| "5", "branch", "compare" | workflows/review-branch.md |
References
- references/review-checklist.md - Comprehensive checklist by category
- references/common-issues.md - Frequently found problems and fixes
- references/security-patterns.md - Security vulnerabilities to watch for
Available Workflows
- review-diff.md - Review current uncommitted changes
- review-staged.md - Review staged changes before commit
- review-pr.md - Review a pull request by number
- review-file.md - Deep review of a specific file
- review-branch.md - Compare branches
Automation Scripts
Optional helper scripts for code review tasks:
- scripts/get-diff.sh - Get formatted git diff (unstaged/staged/branch)
- scripts/check-tests.sh - Verify test coverage for changed files
- scripts/format-report.sh - Generate review report template
Usage:
# Get diff
./scripts/get-diff.sh [unstaged|staged|branch] [branch-name]
# Check test coverage
./scripts/check-tests.sh [unstaged|staged]
# Generate report template
./scripts/format-report.sh "Feature Name"