review
Comprehensive code review workflow - parallel specialized reviews → synthesis
Best use case
review is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Comprehensive code review workflow - parallel specialized reviews → synthesis
Teams using review should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/review/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How review Compares
| Feature / Agent | review | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Comprehensive code review workflow - parallel specialized reviews → synthesis
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# /review - Code Review Workflow
Multi-perspective code review with parallel specialists.
## When to Use
- "Review this code"
- "Review my PR"
- "Check this before I merge"
- "Get feedback on implementation"
- Before merging significant changes
- Quality gates
## Workflow Overview
```
┌──────────┐
│ critic │ ─┐
│ (code) │ │
└──────────┘ │
│
┌──────────┐ │ ┌──────────────┐
│plan-reviewer│ ─┼────▶ │ review-agent │
│ (plan) │ │ │ (synthesis) │
└──────────┘ │ └──────────────┘
│
┌──────────┐ │
│plan-reviewer│ ─┘
│ (change) │
└──────────┘
Parallel Sequential
perspectives synthesis
```
## Agent Sequence
| # | Agent | Focus | Execution |
|---|-------|-------|-----------|
| 1 | **critic** | Code quality, patterns, readability | Parallel |
| 1 | **plan-reviewer** | Architecture, plan adherence | Parallel |
| 1 | **plan-reviewer** | Change impact, risk assessment | Parallel |
| 2 | **review-agent** | Synthesize all reviews, final verdict | After 1 |
## Review Perspectives
- **critic**: Is this good code? (Style, patterns, readability)
- **plan-reviewer**: Does this match the design? (Architecture, plan)
- **plan-reviewer**: Is this change safe? (Risk, impact, regressions)
- **review-agent**: Overall assessment and recommendations
## Execution
### Phase 1: Parallel Reviews
```
# Code quality review
Task(
subagent_type="critic",
prompt="""
Review code quality: [SCOPE]
Evaluate:
- Code style and consistency
- Design patterns used
- Readability and maintainability
- Error handling
- Test coverage
Output: List of issues with severity (critical/major/minor)
""",
run_in_background=true
)
# Architecture review
Task(
subagent_type="plan-reviewer",
prompt="""
Review architecture alignment: [SCOPE]
Check:
- Follows established patterns
- Matches implementation plan (if exists)
- Consistent with system design
- No architectural violations
Output: Alignment assessment with concerns
""",
run_in_background=true
)
# Change impact review
Task(
subagent_type="plan-reviewer",
prompt="""
Review change impact: [SCOPE]
Assess:
- Risk level of changes
- Affected systems/components
- Backward compatibility
- Potential regressions
- Security implications
Output: Risk assessment with recommendations
""",
run_in_background=true
)
# Wait for all parallel reviews
[Check TaskOutput for all three]
```
### Phase 2: Synthesis
```
Task(
subagent_type="review-agent",
prompt="""
Synthesize reviews for: [SCOPE]
Reviews:
- critic: [code quality findings]
- plan-reviewer: [architecture findings]
- plan-reviewer: [change impact findings]
Create final review:
- Overall verdict (APPROVE / REQUEST_CHANGES / NEEDS_DISCUSSION)
- Prioritized action items
- Blocking vs non-blocking issues
- Summary for PR description
"""
)
```
## Review Modes
### Full Review
```
User: /review
→ All four agents, comprehensive review
```
### Quick Review
```
User: /review --quick
→ critic only, fast feedback
```
### Security Focus
```
User: /review --security
→ Add aegis (security agent) to parallel phase
```
### PR Review
```
User: /review PR #123
→ Fetch PR diff, review changes
```
## Example
```
User: /review the authentication changes
Claude: Starting /review workflow...
Phase 1: Running parallel reviews...
┌────────────────────────────────────────────┐
│ critic: Reviewing code quality... │
│ plan-reviewer: Checking architecture... │
│ plan-reviewer: Assessing change impact... │
└────────────────────────────────────────────┘
critic: Found 2 issues
- [minor] Inconsistent error messages in auth.ts
- [major] Missing input validation in login()
plan-reviewer: ✅ Matches authentication plan
plan-reviewer: Medium risk
- Affects: login, signup, password reset
- Breaking change: session token format
Phase 2: Synthesizing...
┌─────────────────────────────────────────────┐
│ Review Summary │
├─────────────────────────────────────────────┤
│ Verdict: REQUEST_CHANGES │
│ │
│ Blocking: │
│ 1. Add input validation to login() │
│ │
│ Non-blocking: │
│ 2. Standardize error messages │
│ │
│ Notes: │
│ - Document session token format change │
│ - Consider migration path for existing │
│ sessions │
└─────────────────────────────────────────────┘
```
## Verdicts
- **APPROVE**: Ready to merge, all issues are minor
- **REQUEST_CHANGES**: Blocking issues must be fixed
- **NEEDS_DISCUSSION**: Architectural decisions need inputRelated Skills
security-review
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
differential-review
Security-focused differential code review with blast radius analysis, risk-adaptive depth (DEEP/FOCUSED/SURGICAL), git history correlation, and structured finding format. Adapted from Trail of Bits. Use when reviewing PRs, commits, or code changes for security implications.
diff-review-strategy
PR size-based review depth, performance review checklist, architecture conformance checks, and framework-specific review patterns.
workflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
wiring
Wiring Verification
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
visual-verdict
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
verification-loop
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.
variant-analysis
Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.
validate-agent
Validation agent that validates plan tech choices against current best practices
tracing-patterns
OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries