Comprehensive code review workflow - parallel specialized reviews → synthesis
npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill review
Multi-perspective code review with parallel specialists.
┌──────────┐
│ critic │ ─┐
│ (code) │ │
└──────────┘ │
│
┌──────────┐ │ ┌──────────────┐
│plan-reviewer│ ─┼────▶ │ review-agent │
│ (plan) │ │ │ (synthesis) │
└──────────┘ │ └──────────────┘
│
┌──────────┐ │
│plan-reviewer│ ─┘
│ (change) │
└──────────┘
Parallel Sequential
perspectives synthesis
| # | 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 |
# 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]
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
"""
)
User: /review
→ All four agents, comprehensive review
User: /review --quick
→ critic only, fast feedback
User: /review --security
→ Add aegis (security agent) to parallel phase
User: /review PR #123
→ Fetch PR diff, review changes
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 │
└─────────────────────────────────────────────┘
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
Comprehensive GitHub code review with AI-powered swarm coordination
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
Take parcadei/review from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.