git:20261014.ce649c0 to git:20261027.ab1f702

14 added, 57 removed. Audit A to A.

---

name: interrogate

- description: "Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles."

+ description: "Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Adversaries try to break a change or design, and only findings proven by a run survive."

disable-model-invocation: true

---

# Interrogate

- Spawn one reviewer per configured 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, 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 with any surrounding context files the reviewers need to understand the code.

- ## Step 2, Intent

- Before spawning 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 you're unsure about the intent, ask the user before proceeding.

- ## Step 3, Spawn Reviewers

- Launch all reviewers in a single message with the Task tool, one per entry on the `interrogate reviewers` line in `~/.cursor/rules/pstack-models.mdc`, labeled Reviewer A, B, and so on to match the entry count. If the rule or that line is missing, use the table defaults.

- | Subagent | Default model |

- |----------|---------------|

- | Reviewer A | `claude-opus-5-5-xhigh` |

- | Reviewer B | `grok-4.7-xhigh-fast` |

- Each reviewer gets `subagent_type: generalPurpose`, `readonly: true`, and `model` set to its configured entry, or its table default when there is no configured line. Omit `model` for an `auto` or `inherit-parent` entry, so that reviewer runs on the parent model.

- If the Task tool rejects a configured entry, run that reviewer on its family's table default and say so. Families go by prefix: `claude-*`, and `grok-*` with `cursor-grok-*` and `composer-*`. A refused `composer-*` entry runs on Reviewer B's default. With no family match, use Reviewer A's default. If it rejects a table default, spawn with the closest equivalent from the valid slugs in its error message (prefer the same family and reasoning tier), and open a separate PR to update the default table. Do not block the review on the slug issue. Never treat an alias entry as a rejected slug or apply either fallback to it.

- Read `references/reviewer-prompt.md` and fill in the same template for every reviewer with the stated intent, the diff or file contents, the rubric from `references/rubric.md`, and the code-quality lens from `references/code-quality-review.md`. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the **poteto-mode** skill.

- ## Step 4, Synthesize

- As results come back, build a unified picture. Parse every reviewer's findings. Merge findings that describe the same issue differently, and note which models raised each one. Findings two or more models raised independently are the highest signal. Read a lone model's finding, but weight it accordingly. Note disagreements. If one model flags something and another explicitly says the opposite, that is context for the verdict.

- ## Step 5, Lead Judgment

+ Adversaries try to break a change or a design. A finding survives only when a run proves it. Report the findings. Do not apply fixes.

- You are the lead reviewer, a pragmatic senior engineer, not a neutral aggregator. Read `references/lead-judgment.md` for the full framework. Put every finding in one of four buckets, with the model(s) that raised it and a one-line rationale.

+ ## Frame

- - **Act on**. Real issues affecting correctness, security, or maintainability given the actual goals. They would block a real PR.

- - **Consider**. Legitimate, but you're not sure they outweigh the cost of addressing them now. Worth the user's attention.

- - **Noted**. Technically valid but not actionable. Context-dependent, premature optimization, or low-impact at this stage.

- - **Dismissed**. Wrong, nitpicky, or missing context, with a brief reason.

+ The scope is what the user names. Otherwise it is the branch diff from its merge base with the base branch, through the working tree. State the intent with the **in-your-own-words** skill, from the user's message, the commits, and the PR description. Ask the user when the intent is unclear.

- ## Output Format

+ ## Fan out

- ### Intent

- > [The stated intent paragraph from Step 2]

+ Run Phase A steps 3 and 4 and Phase B of the **arena** skill, with four changes. Read the `interrogate reviewers` line in place of `arena runners`. Copy the scope's uncommitted changes into each worktree. Spawn each adversary as `generalPurpose`. In place of the arena task and rationale, give each adversary the scope, the intent, and this brief:

- ### Reviewers

- - Reviewer [label]: [model name], [N findings] (one bullet per reviewer)

+ > Break this change. Prove each finding with a run against the real code, such as a failing test, a repro script, or command output that shows the wrong behavior. For a design or plan, run a prototype or probe the current tree. Keep repros in your own worktree. Report each finding with a title, the exact command, the output it printed, and the output the intent requires. Leave out anything you did not run. That covers style, naming, structure, and risks that need a future change to matter. No findings is a valid result.

- ### Act On

- [Each: description, which models raised it, why it matters.]

+ ## Verify

- ### Consider

- [Each: description, which models raised it, the tradeoff.]

+ Verify each finding per arena Phase F by rerunning its command. Keep a finding when the output shows the failure and the failure breaks the intent. Drop the rest. Merge findings that share a root cause.

- ### Noted

- [Brief list.]

+ Skip arena Phases C, D, and E. Adversaries find different failures, so the verdict keeps every verified finding, not one adversary's list.

- ### Dismissed

- [Each with a brief rationale.]

+ ## Output

- ### Agreement Map

- [Where models agreed and diverged, and what that pattern tells us.]

+ - **Intent**: the restatement.

+ - **Findings**: for each verified finding, the command, its output, how it breaks the intent, and the adversaries that found it. Say "no verified findings" when none survive.

+ - **Dropped**: for each adversary, the count of dropped findings and why.