interrogate

Interrogate

Spawn one reviewer per configured model to adversarially review code changes. Each model gets the same prompt and rubric. The adversarial signal comes from model diversity, not assigned personas. Models differ in blind spots, priors, and reasoning patterns. Agreement across models is high-confidence signal; lone-model findings are worth reading but lower confidence.

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, run git diff main...HEAD (or the appropriate base branch) for the full changeset
• 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:

• The user's message
• Commit messages
• PR description if one exists
• The code itself

Write one clear paragraph. Reviewers challenge whether the work achieves the intent well, not whether the intent itself is correct. If you're unsure about the intent, ask the user before proceeding.

Step 3, Spawn Reviewers

Launch all reviewers in a single message using the Task tool. Spawn one reviewer per Reviewer A/B/C/D label below. Vary the model between them where the Agent tool allows it, so the panel is not four copies of one model's blind spots.

Subagent	Default model
Reviewer A	claude-fable-5-thinking-max
Reviewer B	gpt-5.6-sol-max
Reviewer C	grok-4.6-fast-xhigh
Reviewer D	claude-opus-5-thinking-xhigh

For each reviewer:

• subagent_type: generalPurpose
• model: the configured interrogate reviewers entry, or the table default with no configured line
• readonly: true

If a model slug is rejected as unresolvable when you try to spawn the subagent, check the valid slugs in the Task tool's error message, pick the closest equivalent (prefer the highest-reasoning tier of the same family), spawn with the valid slug, and open a separate PR to update the configured value or default table. Do not block the review on the slug issue. If the configured value is inherit-parent or auto, omit model instead; never treat those aliases as broken slugs or enter this fallback for them.