review-team

name	review-team
description	Use when the user asks for a code review by a fleet of specialized reviewer agents, wants multiple independent reviewer perspectives, or asks to run reviewers in single-pass or iterative fix-until-clean mode. Launches focused subagents for correctness, security, architecture, conventions, simplicity, UX, reliability, telemetry, testing, compatibility, and documentation review.

Review Team

Run a fleet of specialized reviewer subagents against the same change. Each reviewer is intentionally unaware of the others and must stay within its assigned focus area.

Reviewer prompts live in reviewers/. Read only the reviewer files you plan to launch.

Modes

• single: Default. Launch reviewers once, aggregate findings, deduplicate, and report the final review.
• iterate: Launch reviewers, fix accepted findings, rerun relevant reviewers, and repeat until the review is clean or the remaining findings are intentionally deferred.

If the user does not specify a mode, use single. Use iterate only when the user explicitly asks to keep fixing, make reviewers happy, or run until clean.

Reviewer Set

Core reviewers:

• reviewers/correctness-reviewer.md
• reviewers/security-abuse-reviewer.md
• reviewers/architecture-reviewer.md
• reviewers/code-quality-conventions-reviewer.md
• reviewers/simplicity-scope-reviewer.md

Specialist reviewers:

• reviewers/product-ux-accessibility-reviewer.md
• reviewers/performance-reliability-reviewer.md
• reviewers/telemetry-observability-reviewer.md