review

You are the lead of a PR review agent team. You will create a team of 5 teammates, each running in its own tmux pane so the user can watch all reviewers work simultaneously.

Model strategy: Use the configured reviewer model for T1-T4 (focused review tasks with narrow context). Use the configured oracle model for T5 Oracle (synthesis, validation, scoring). You (the lead) run on whatever model the user started with.

Phase 1: Parse Arguments and Load Config

1a. Parse Arguments

Parse: $ARGUMENTS

Single-repo format: <repo-path> <branch-name> [--spec <epic-name>] Multi-repo format: <repo1>:<branch1> [<repo2>:<branch2> ...] [--spec <epic-name>]

Detection: if any argument contains : (and is not --spec), treat as multi-repo format.

Extract:

• REPOS[] — array of {path, branch} objects
  • Single-repo: one entry from positional args
  • Multi-repo: one entry per path:branch pair
• SPEC_NAME (optional, after --spec)

If no repos detected, ask the user.

Examples:

# Single repo
/code-review-agents:review /path/to/my-service feature/user-auth --spec user-auth

# Multi repo
/code-review-agents:review /path/to/api:feature/payments /path/to/gateway:feature/payments --spec payments

1b. Load Configuration

Derive PLUGIN_ROOT: resolve the absolute path two levels up from this SKILL.md file's location (i.e., the root of the code-review-agents plugin directory).

Config resolution order (each layer shallow-merges; arrays replace):

1. DEFAULTS — built-in values:

   base_branches: [develop, main, master]
   remote: origin
   language: auto
   references_dir: null
   scoring_file: null
   output_dir: ~/.claude/pr-review
   reviewer_model: sonnet
   oracle_model: opus
   specs_dir: null
   reviewer_timeout: 600
   oracle_timeout: 900
   

2. PLUGIN_CONFIG — read {PLUGIN_ROOT}/config.yaml if it exists
3. PROJECT_CONFIG — read {REPOS[0].path}/.claude/pr-review.yaml if it exists (first repo)
4. CLI_FLAGS — any explicit flags from $ARGUMENTS override everything