description: Comprehensive PR review using specialized agents - comments, tests, errors, types, code quality, docs, and simplification argument-hint: "<pr-number> [aspects: comments|tests|errors|types|code|docs|simplify|all]"

Comprehensive PR Review with Specialized Agents

Run a multi-agent review on a pull request, with each agent focusing on a specific aspect of code quality.

Target: $ARGUMENTS

Pre-Review Setup

Before running reviews:

1. Identify the PR

   • If PR number provided: gh pr view <number>
   • If no number: gh pr view (current branch's PR)
   • Get PR branch name and changed files

2. Check PR State

   • Is rebase needed? Check if behind base branch
   • Are there conflicts? Resolve intelligently if needed
   • Never push to main without explicit user approval

3. Get Changed Files

   gh pr diff <number> --name-only
   

Review Aspects

Aspect Selection Logic

Always run:

• code-reviewer - Core quality check

Almost always run (skip only for trivial PRs):

• docs-impact-agent - Identifies stale or missing docs

Skip docs-impact-agent only when:

• Typo-only fixes (comments, strings)
• Test-only changes (no production code)
• Documentation-only changes
• Config tweaks (CI, linting)

Run based on changes:

• Test files changed → pr-test-analyzer
• Comments/docstrings added → comment-analyzer
• Try-catch or error handling → silent-failure-hunter
• New types or type modifications → type-design-analyzer

Run last:

• code-simplifier - After other reviews pass

Execution

Sequential (Default)

Run agents one at a time for clear, actionable feedback:

1. code-reviewer - Guidelines and bugs
2. docs-impact-agent - Identify stale or missing docs
3. Applicable specialist agents based on changes
4. code-simplifier - Identify simplification opportunities (if requested or all reviews pass)

Parallel (When Requested)

If user specifies "parallel", launch all applicable agents simultaneously using multiple Task tool calls in one message.

Agent Instructions

When launching each agent via Task tool:

code-reviewer:

Review PR #<number> for project guideline compliance, bugs, and quality issues. Focus on the diff. Report only high-confidence issues (80+).

docs-impact-agent:

Review PR #<number> and identify any documentation affected by these changes. Check CLAUDE.md, README.md, and docs/ for stale, incorrect, or missing content. Report findings with specific file locations and suggested fixes. Do not modify files or commit.

pr-test-analyzer:

Analyze test coverage for PR #<number>. Focus on behavioral coverage, identify critical gaps, rate recommendations by criticality.

comment-analyzer:

Analyze code comments in PR #<number> for accuracy, completeness, and long-term value. Verify comments match actual code behavior.

silent-failure-hunter:

Hunt for silent failures in PR #<number>. Check all error handling for proper logging, user feedback, and specific catch blocks.

type-design-analyzer:

Analyze type design in PR #<number>. Rate encapsulation, invariant expression, usefulness, and enforcement. Focus on new or modified types.

code-simplifier:

Identify simplification opportunities in PR #<number> for clarity while preserving functionality. No nested ternaries, prefer explicit over clever. Report findings with before/after suggestions. Do not modify files or commit.

Result Aggregation

After all agents complete, aggregate findings:

Categories

Summary Format

## PR Review Summary

### Critical Issues (X found)
| Agent | Issue | Location |
|-------|-------|----------|
| code-reviewer | Description | `file.ts:line` |

### Important Issues (X found)
| Agent | Issue | Location |
|-------|-------|----------|
| silent-failure-hunter | Description | `file.ts:line` |

### Suggestions (X found)
| Agent | Suggestion | Location |
|-------|------------|----------|
| type-design-analyzer | Description | `file.ts:line` |

### Strengths
- Well-structured error handling
- Good test coverage for critical paths

### Documentation Issues
- `CLAUDE.md` - Stale command reference needs update
- `README.md` - Configuration section outdated

### Verdict
[READY TO MERGE / NEEDS FIXES / CRITICAL ISSUES]

### Recommended Actions
1. Fix critical issues first
2. Address important issues
3. Consider suggestions
4. Re-run review after fixes

Post to GitHub

Always post the summary to the PR when a PR number is provided:

gh pr comment <PR_NUMBER> --body "<summary>"

Usage Examples

# Full review of specific PR
/prp-review-agents 163

# Review only specific aspects
/prp-review-agents 163 tests errors

# Review current branch's PR
/prp-review-agents

# Only code and docs review
/prp-review-agents 42 code docs

# All reviews in parallel
/prp-review-agents 42 all parallel

# Just simplify after passing review
/prp-review-agents 42 simplify

Workflow Integration

Before creating PR:

1. Run /prp-review-agents on current branch
2. Fix critical and important issues
3. Re-run to verify
4. Create PR

During PR review:

1. Run /prp-review-agents <pr-number>
2. Review posts summary to GitHub
3. Address feedback
4. Re-run targeted aspects

After making changes:

1. Run specific aspects: /prp-review-agents <pr-number> tests code
2. Verify issues resolved
3. Push updates

Notes

• Agents analyze git diff by default (changed files only)
• Each agent returns detailed report with file:line references
• All agents are advisory — they report findings but do not modify files or commit
• Summary always posted as PR comment when PR number provided