Interrogate

Spawn independent reviewers to adversarially review code changes. Every reviewer gets the same prompt and rubric. Prefer different model families when the host supports model selection; otherwise use fresh isolated contexts. Agreement across reviewers is high-confidence signal; lone-reviewer findings remain useful but carry less weight.

The deliverable is a synthesized verdict. Do NOT auto-apply changes.

Step 1, Determine Scope

Identify what to review from context:

• If the user points at specific files or a diff, use that
• If on a feature branch, diff against the repository's declared target or merge base (for example git diff origin/main...HEAD)
• If the user's message references recent work, gather the relevant files

Package the diff (or file contents) plus any surrounding context files the reviewers need to understand the code.

Step 2, State the Intent

Before spawning reviewers, state the intent explicitly. What is this code trying to accomplish? Derive this from: