multi-reviewlisted

# Multi-Reviewer — orchestrated specialist code review You are orchestrating a **multi-reviewer team**: a small cast of niche specialist sub-agents that each review the diff from a single angle. **You** read the full specialist reports, dedupe findings, and produce the final report directly. Specialists run **in parallel**. This skill is distinct from the existing single-reviewer `reviewer` agent and the pre-implementation `three-reviewer-parallel-mandates-pattern` knowledge entry: - **Use `reviewer` agent** for tiny diffs (≤10 lines, single domain). - **Use three-reviewer parallel-mandates** for **pre-implementation** plan review (critic / pragmatist / security against a draft plan — no code yet). - **Use multi-reviewer (this skill)** for **post-implementation** code review of a non-trivial diff that touches multiple domains. ## When to invoke Trigger phrases / explicit invocations: - `/multi-review` (slash command — primary entry) - "multi-reviewer" - "review with the team" - "review this PR with specialists" - "team review" - "thorough review of my changes" - "review my branch with all the reviewers" **Use it for**: non-trivial diffs spanning multiple domains (e.g. Cloud Functions + frontend + security implications), pre-merge safety on critical paths, production-bound changes touching auth/payments/data. **Do NOT use it for**: - Tiny diffs (≤10 lines, one file) — use the existing `reviewer` agent. - Plan/spec review (no code written yet) — use `three-reviewer-p