Review Panel

One PR, many eyes, one report. A slice PR into an integration branch gets review-pr and a single fresh reviewer. The PR that takes the integration branch to main is larger, final, and about to leave the orchestrator's control, so it gets a panel: several reviewer personas reading the same diff from different angles, in parallel, each returning findings in one schema. You dedup, gate, and write the report. You never edit code and you never merge.

Usage: /review-panel <pr# | PR URL>

0. Is this the right tool?

• The PR's base is the repo's default branch (or the branch the user names as the release line). If the base is an integration branch, stop and run /review-pr instead; a panel on a slice is noise at nine times the cost.
• The PR is open and not a draft. Closed or merged → stop.
• If it closes or references an epic, review-pr's full-epic mode owns the spec verdict; this skill wraps it. Otherwise the PR body is the spec, and say so under Coverage.

Announce the persona set before dispatching (step 3) so the user can trim it.

1. Gather once, share with everyone