Interrogate

Start one reviewer per panel model to adversarially review code changes. The adversarial signal comes from model diversity, not assigned personas. The deliverable is a synthesized verdict. Do NOT auto-apply changes.

Step 1, 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 merge base with the default branch (git diff $(git merge-base HEAD origin/HEAD), else main or master) for the full changeset, including uncommitted changes.
• If the user's message references recent work, gather the relevant files.

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

Step 2, Intent

Before starting reviewers, state the intent in one clear paragraph from the user's message, commit messages, the PR description if one exists, and the code. If the intent is unclear, state your best reading and proceed. The user can redirect.

Step 3, Start reviewers