Review PR

Deep code review using 6-7 parallel specialized agents.

Quick Start

bash

/review-pr 123
/review-pr feature-branch

Opus 4.6: Parallel agents use native adaptive thinking for deeper analysis. Complexity-aware routing matches agent model to review difficulty.

STEP 0: Verify User Intent with AskUserQuestion

BEFORE creating tasks, clarify review focus:

python

AskUserQuestion(
  questions=[{
    "question": "What type of review do you need?",
    "header": "Focus",
    "options": [
      {"label": "Full review (Recommended)", "description": "Security + code quality + tests + architecture"},
      {"label": "Security focus", "description": "Prioritize security vulnerabilities"},
      {"label": "Performance focus", "description": "Focus on performance implications"},
      {"label": "Quick review", "description": "High-level review, skip deep analysis"}
    ],
    "multiSelect": false
  }]
)

Based on answer, adjust workflow:

Full review: All 6-7 parallel agents
Security focus: Prioritize security-auditor, reduce other agents
Performance focus: Add frontend-performance-engineer agent
Quick review: Single code-quality-reviewer agent only

STEP 0b: Select Orchestration Mode

See Orchestration Mode Selection

CRITICAL: Task Management is MANDATORY (CC 2.1.16)

BEFORE doing ANYTHING else, create tasks to track progress:

python

# 1. Create main review task IMMEDIATELY
TaskCreate(
  subject="Review PR #{number}",
  description="Comprehensive code review with parallel agents",
  activeForm="Reviewing PR #{number}"
)

# 2. Create subtasks for each phase
TaskCreate(subject="Gather PR information", activeForm="Gathering PR information")
TaskCreate(subject="Launch review agents", activeForm="Dispatching review agents")
TaskCreate(subject="Run validation checks", activeForm="Running validation checks")
TaskCreate(subject="Synthesize review", activeForm="Synthesizing review")
TaskCreate(subject="Submit review", activeForm="Submitting review")

# 3. Update status as you progress
TaskUpdate(taskId="2", status="in_progress")  # When starting
TaskUpdate(taskId="2", status="completed")    # When done

Phase 1: Gather PR Information

bash

# Get PR details
gh pr view $ARGUMENTS --json title,body,files,additions,deletions,commits,author

# View the diff
gh pr diff $ARGUMENTS

# Check CI status
gh pr checks $ARGUMENTS

Identify: total files changed, lines added/removed, affected domains (frontend, backend, AI).

Tool Guidance

Task	Use	Avoid
Fetch PR diff	`Bash: gh pr diff`	Reading all changed files individually
List changed files	`Bash: gh pr diff --name-only`	`bash find`
Search for patterns	`Grep(pattern="...", path="src/")`	`bash grep`
Read file content	`Read(file_path="...")`	`bash cat`
Check CI status	`Bash: gh pr checks`	Polling APIs

<use_parallel_tool_calls> When gathering PR context, run independent operations in parallel:

```
gh pr view
```
(PR metadata),
```
gh pr diff
```
(changed files),
```
gh pr checks
```
(CI status)

Spawn all three in ONE message. This cuts context-gathering time by 60%. For agent-based review (Phase 3), all 6 agents are independent -- launch them together. </use_parallel_tool_calls>

Phase 2: Skills Auto-Loading (CC 2.1.6)

CC 2.1.6 auto-discovers skills -- no manual loading needed!

Relevant skills activated automatically:

```
code-review-playbook
```
-- Review patterns, conventional comments
```
security-scanning
```
-- OWASP, secrets, dependencies
```
type-safety-validation
```
-- Zod, TypeScript strict
```
testing-patterns
```
-- Test adequacy, coverage gaps, rule matching

Phase 3: Parallel Code Review (6 Agents)

See Agent Prompts -- Task Tool Mode for the 6 parallel agent prompts.

See Agent Prompts -- Agent Teams Mode for the mesh alternative.

See AI Code Review Agent for the optional 7th LLM agent.

Phase 4: Run Validation

See Validation Commands

Phase 5: Synthesize Review

Combine all agent feedback into a structured report. See Review Report Template

Phase 6: Submit Review

bash

# Approve
gh pr review $ARGUMENTS --approve -b "Review message"

# Request changes
gh pr review $ARGUMENTS --request-changes -b "Review message"

CC 2.1.20 Enhancements

PR Status Enrichment

The

pr-status-enricher

hook automatically detects open PRs at session start and sets:

```
ORCHESTKIT_PR_URL
```
-- PR URL for quick reference
```
ORCHESTKIT_PR_STATE
```
-- PR state (OPEN, MERGED, CLOSED)

Session Resume with PR Context (CC 2.1.27+)

Sessions are automatically linked when reviewing PRs. Resume later with full context:

bash

claude --from-pr 123
claude --from-pr https://github.com/org/repo/pull/123

Task Metrics (CC 2.1.30)

See Task Metrics Template

Conventional Comments

Use these prefixes for comments:

```
praise:
```
-- Positive feedback
```
nitpick:
```
-- Minor suggestion
```
suggestion:
```
-- Improvement idea
```
issue:
```
-- Must fix
```
question:
```
-- Needs clarification

Related Skills

commit: Create commits after review
create-pr: Create PRs for review
slack-integration: Team notifications for review events

References

Review Template
Review Report Template
Orchestration Mode Selection
Validation Commands
Task Metrics Template
Agent Prompts -- Task Tool
Agent Prompts -- Agent Teams
AI Code Review Agent

review-pr

NPX Install

SKILL.md Content

Review PR

Quick Start

STEP 0: Verify User Intent with AskUserQuestion

STEP 0b: Select Orchestration Mode

CRITICAL: Task Management is MANDATORY (CC 2.1.16)

Phase 1: Gather PR Information

Tool Guidance

Phase 2: Skills Auto-Loading (CC 2.1.6)

Phase 3: Parallel Code Review (6 Agents)

Phase 4: Run Validation

Phase 5: Synthesize Review

Phase 6: Submit Review

CC 2.1.20 Enhancements

PR Status Enrichment

Session Resume with PR Context (CC 2.1.27+)

Task Metrics (CC 2.1.30)

Conventional Comments

Related Skills

References