From code-review
This skill should be used when the user asks about "code review best practices", "how to review code", "review methodology", "code review framework", "impact prioritization", "root cause analysis", or needs guidance on systematic code review approaches and output templates.
How this skill is triggered — by the user, by Claude, or both
Slash command
/code-review:code-review-patternsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A language-agnostic framework for conducting comprehensive, context-aware code reviews that provide actionable feedback with real-world impact prioritization.
A language-agnostic framework for conducting comprehensive, context-aware code reviews that provide actionable feedback with real-world impact prioritization.
Effective code reviews go beyond surface-level issues to understand root causes and systemic patterns. Focus on providing deep, actionable feedback that considers business context, not just technical correctness.
Key principles:
Before reviewing, establish context from the project itself:
The codebase itself defines what "good" looks like - discover and apply those standards.
For every issue, provide three levels of analysis:
Level 1 - What: The immediate issue observed Level 2 - Why: Root cause analysis explaining why this happens Level 3 - How: Specific, actionable solution with working code
This ensures issues are fully understood and solutions address underlying problems, not just symptoms.
Classify every issue by real-world impact:
| Priority | Label | Criteria | Action |
|---|---|---|---|
| CRITICAL | Red | Security vulnerabilities, data loss risks, privacy violations, production crashes | Fix immediately |
| HIGH | Orange | Performance in hot paths, resource leaks, broken error handling, missing validation | Fix before merge |
| MEDIUM | Yellow | Maintainability issues, inconsistent patterns, missing tests, tech debt in active areas | Fix soon |
| LOW | Green | Style inconsistencies, minor optimizations, documentation gaps | Fix when convenient |
Comprehensive reviews cover six specialized aspects:
For detailed guidance on each aspect, see references/review-aspects.md.
Comprehensive review requires understanding relationships:
Find related files before concluding a review is complete.
Apply five layers of analysis:
Never just identify problems - always show the fix. A quality issue report includes:
Adapt solutions to match the codebase's existing patterns and conventions.
Structure feedback consistently:
# Code Review: [Scope]
## Review Metrics
- **Files Reviewed**: X
- **Critical Issues**: X
- **High Priority**: X
- **Medium Priority**: X
- **Suggestions**: X
## Executive Summary
[2-3 sentences summarizing the most important findings]
## CRITICAL Issues (Must Fix)
[Issues with root cause analysis and working solutions]
## HIGH Priority (Fix Before Merge)
[Issues with root cause analysis and working solutions]
## MEDIUM Priority (Fix Soon)
[Issues with root cause analysis and working solutions]
## LOW Priority (Opportunities)
[Suggestions and minor improvements]
## Strengths
[What's done well, patterns worth replicating]
## Proactive Suggestions
[Opportunities beyond identified issues]
## Systemic Patterns
[Issues appearing multiple times - candidates for team discussion]
For detailed patterns and guidance, consult:
references/focus-areas.md - Canonical definitions of the 6 focus areas with priority factorsreferences/review-aspects.md - Deep dive into each review aspect with checklistsA quality review should:
npx claudepluginhub betamatt/claude-plugins --plugin code-reviewConducts code reviews of pull requests and changes for correctness, security, performance, and maintainability with actionable feedback grouped by severity levels.
Guides effective code reviews with mindset, actionable feedback examples, scope, and phased process. Use for pull requests, standards, mentoring, architecture reviews.
Structured code review that composes validation checklists from relevant atoms based on code changes. Produces severity-ordered report with specific locations and fixes. Activated when user asks for code review.