MCPInstall

review

Comprehensive code review workflow - parallel specialized reviews → synthesis

Installs
519
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/parcadei/continuous-claude-v3 --skill review
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads review automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

/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

#AgentFocusExecution
1criticCode quality, patterns, readabilityParallel
1plan-reviewerArchitecture, plan adherenceParallel
1plan-reviewerChange impact, risk assessmentParallel
2review-agentSynthesize all reviews, final verdictAfter 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 input

FAQ

What does the review skill do?

Comprehensive code review workflow - parallel specialized reviews → synthesis

How do I install review?

Run npx skills add https://github.com/parcadei/continuous-claude-v3 --skill review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/review/ (personal) or .claude/skills/review/ (project).

Which AI agents can use review?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is review safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains review?

It is published by parcadei in parcadei/continuous-claude-v3. It has 519 recorded installs.

More from parcadei/continuous-claude-v3

View all →

discovery-interview

parcadei/continuous-claude-v3

Deep interview process to transform vague ideas into detailed specs. Works for technical and non-technical users.

4.1K installs

premortem

parcadei/continuous-claude-v3

Identify failure modes before they occur using structured risk analysis

886 installs

math

parcadei/continuous-claude-v3

Unified math capabilities - computation, solving, and explanation. I route to the right tool.

github-search

parcadei/continuous-claude-v3

Search GitHub code, repositories, issues, and PRs via MCP

AI & Agents732 installs

dead-code

parcadei/continuous-claude-v3

Find unused functions and dead code in the codebase

refactor

parcadei/continuous-claude-v3

Code refactoring workflow - analyze → plan → implement → review → validate

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.