Interrogate

On Codex, read the platform mapping, including its per-skill notes, before following this skill.

On GitHub Copilot, read the platform mapping, including its per-skill notes, before following this skill.

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 Agent tool, one per entry on the interrogate reviewers line in pstack-models.md, labeled Reviewer A, B, and so on to match the entry count. If the sheet or that line is missing, use the table defaults.

Subagent	Default model
Reviewer A	opus
Reviewer B	fable
Reviewer C	sonnet
Reviewer D	haiku

Each reviewer gets subagent_type: "general-purpose", 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 Agent tool rejects a configured entry, run that reviewer on its family's table default and say so. Families go by model name, such as Opus, Fable, or Sonnet. 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.

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

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.

• 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.

Output Format

Intent

[The stated intent paragraph from Step 2]

Reviewers

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

Act On

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

Consider

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

Noted

[Brief list.]

Dismissed

[Each with a brief rationale.]

Agreement Map

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

Reasoning effort

A role value in the override sheet may name a reasoning effort after its model, as in opus @xhigh. Levels on Claude Code: low, medium, high, xhigh, max. Which ones apply depends on the model. A value without @ takes the sheet's default effort line, a level or session, and session when the sheet has no such line. session sets no effort, so the dispatch is the usual one. Strip the suffix before reading the model: inherit-parent or auto still omits model at every level, and a model name is passed as model. On Claude Code, a level picks the effort agent from the subagent_type you would otherwise use. pstack:poteto-agent becomes subagent_type: "pstack:poteto-agent-<level>". general-purpose, or no subagent_type, becomes subagent_type: "pstack:effort-<level>". The effort agents set only effort, so the model you pass still decides the model. On Codex, pass the level as spawn_agent's reasoning_effort and keep the usual instructions.