pr-review

PR Review Command

ultrathink

Respond to PR review comments for: $ARGUMENTS

Load configuration from .claude/commands/pr-review-config.yaml for scripts, completion criteria, error recovery, and failure handling tables.

Context

• Current branch: !git branch --show-current
• Repository: !gh repo view --json nameWithOwner -q '.nameWithOwner'
• Authenticated as: !gh api user -q '.login'

Arguments

Argument	Description	Default
PR_NUMBERS	Comma-separated PR numbers or all-open	Required
--parallel	Use git worktrees for parallel execution	false
--cleanup	Clean up worktrees after completion	true
--dry-run	Preview planned actions without executing (JSON output)	false

Workflow

When --dry-run is specified, gather read-only context and output planned actions as JSON. See dry_run in config for output schema and constraints. Exit after output without executing mutations.

Step 1: Parse and Validate PRs

For all-open, query open PRs. Cap the list to invocation_limits.all_open_max_prs from config (default: 5). If more open PRs exist, report the overflow count and execute invocation_limits.all_open_overflow_action.

For each PR number, validate using scripts.claude_code.get_pr_context from config.

Verify PR merge state using scripts.claude_code.test_pr_merged. Exit code 0 = not merged (safe), 1 = merged (skip). This avoids stale state from gh pr view.

Step 2: Comprehensive PR Status Check

Before addressing comments, gather full context:

1. Review ALL comments: Use get_review_threads, get_unresolved_threads, get_unaddressed_comments, and get_pr_context scripts from config.
2. Check merge eligibility: Verify mergeable=MERGEABLE and no conflicts.
3. Review failing checks: Use get_pr_checks script. Handle failures per check_failure_actions table in config.

Step 3: Create Worktrees (if --parallel)

branch=$(gh pr view {number} --json headRefName -q '.headRefName')
git worktree add "./.worktrees/pr-{number}" "$branch"

Step 4: Launch Agents

Sequential: Invoke pr-comment-responder skill for each PR with session context at .agents/pr-comments/PR-{pr}/.

Parallel: Launch background Task agents per PR. Wait for all with TaskOutput.

Each agent's intermediate output is subject to output_constraints.per_pr_max_response_tokens from config. If an agent approaches the token limit, summarize findings and move to the next PR.

Step 5: Verify, Push, and Cleanup

Push any changes per worktree. Clean up worktrees if --cleanup. Check worktree_constraints in config for isolation rules.

Step 6: Generate Summary

Report per-PR status using output_constraints.summary_format from config. Required columns: output_constraints.summary_required_columns. The only currently supported value of summary_format is table, so render a markdown table with one row per PR. If a future config introduces another value, update both this step and the allowed values in output_constraints.summary_format together.

Thread Resolution

Replying does NOT resolve threads. Use add_thread_reply_resolve or separate resolve_thread calls. For batch resolution, use the GraphQL template in config.

Completion Gate

ALL criteria from completion_criteria in config must pass before claiming completion. If ANY fails, loop back up to invocation_limits.completion_gate_max_retries times (default: 3) from config. If criteria still fail after the maximum retries, execute invocation_limits.completion_gate_overflow_action and halt. See failure_handling and error_recovery in config for recovery actions.

Related Memories

See related_memories in config for Serena memories to consult during PR review.