code-reviewers

What problem does it solve?

Dispatch a team of two competing reviewers to critique a diff, challenge each other's findings, and produce a high-signal report. Use this when the user asks for a thorough code review, wants a second opinion before committing, or wants findings that have survived adversarial scrutiny. Prefer this over the solo code-review skill when rigour matters more than speed. Invoke with /code-reviewers.

Core Features & Use Cases

• Independent reviews: two reviewers independently assess the diff to surface diverse perspectives.
• Adversarial challenge: reviewers challenge each other's findings, strengthening trust in the final report.
• Consolidated output: produces a four-bucket report highlighting consensus, survived challenges, contested items, and single-reviewer notes.
• Ideal when time, rigor, and traceability matter, such as audits, open-source contributions, or critical production changes.

Quick Start

Spawn two reviewers and start an adversarial review of the current diff.