Code reviewers

A team version of the code-review skill. Two reviewers inspect the diff independently, then challenge each other's findings. A finding only reaches the final report if it survives scrutiny -- or if it's serious enough to surface even uncontested. The adversarial step is where the signal lives: anything that survives a capable opponent's challenge is worth your attention.

Use this when the user wants a thorough review with adversarial rigour. For a quick solo pass, use the code-review skill instead.

Before you start

Inspect the changes yourself first, so you can brief the reviewers. On the main branch, that's typically the (staged) git diff. On a feature branch, that's the committed and uncommitted changes compared to main. The reviewers will inspect the diff themselves too -- your inspection is just so you know what they're walking into.

Flow

1. Use the session's team -- it forms when the first reviewer is spawned; there's nothing to set up.
2. Spawn two reviewers from the roster, both in the background, both with the shared prompt below.
3. Reviewers run three phases: independent review, then challenge, then defend or concede. All coordination is via SendMessage.
4. Collect self-reports from each reviewer.
5. Consolidate into a four-bucket report for the user.
6. Clean up by shutting down the reviewers.