pr-review-team

PR Review Team

MANDATORY first step — BEFORE any Agent / Read / bash work:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/pr-review-state.sh init <PR番号>

State init gives the leader (and the user reading the transcript) a visible audit trail of the review loop. Retroactively creating the state file after agents have already spawned defeats that purpose — if you skipped init, restart the loop rather than paper over it. Run init now.

---

MANDATORY: This skill runs a complete review-fix-re-review loop using Subagents (NOT Agent Teams).

The leader MUST:

1. Initialize state and gather PR context (Step 1)
2. Select and launch the parallel reviewer subagents (Step 2 — the selector decides which of the 4 run)
3. Run CI checks via script (Step 3)
4. Integrate results + security checklist (Step 4)
5. If critical > 0 OR important > 0 OR security != "all_pass": enter fix loop (Step 5)
6. Report results and cleanup (Step 6)

🔴 These steps are mandatory. The leader is accountable for completing every step — skipping is a workflow violation.

Step 1: Initialize & Identify Target PR

Initialize State

Run immediately (creates the active-review state file for audit visibility):

bash ${CLAUDE_PLUGIN_ROOT}/scripts/pr-review-state.sh init <PR番号>

Resolve PR

• If user specified: use that number
• Otherwise: gh pr view --json number --jq '.number' 2>/dev/null

Gather Context

• File overview: gh pr diff <PR番号> --name-only
• Base branch: git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|refs/remotes/origin/||' (fallback: main)
• Test command: detect from package.json, Makefile, pytest.ini, etc.
• Project rules: read project's CLAUDE.md if present

Note: gh commands rely on sandbox.network.allowedDomains (github.com, api.github.com) in ~/.claude/settings.json to run inside the sandbox without prompts. Do NOT pass dangerouslyDisableSandbox: true defensively — the flag forces an auto-mode-refused approval prompt that breaks the review flow (see Issue #245).