interrogate · git:20261109.c998def · 2026-11-09 · sha256 ae1d0ec1534c1529
interrogate git:20261109.c998defA
Immutable. This exact content never changes and is served at /api/v1/blob/ae1d0ec1534c1529.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qvdr2sgjvskzahq3/ae1d0ec1534c1529867b8ac579559673b056cc089776a5ce305687683e3247dd.json
Then /plugin install interrogate@markdownregistry-qvdr2sgjvskzahq3 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- 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.' disable-model-invocation: true --- # 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. 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 develop...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. Derive this from: - The user's message - Commit messages - PR description if one exists - The code itself Write one clear paragraph. If you're unsure about the intent, ask the user before proceeding. ## Step 3, Spawn Reviewers Launch all reviewers in a single turn, one `delegate_task` per reviewer with `mode: "async"`. Use the `interrogate reviewers` line in `p3-models.md`, one reviewer per entry, labeled Reviewer A, B, C, and so on for the configured entry count. Resolve each entry's provider and model through `orchestrator_capabilities`. If the line is missing, run `setup-p3` first. For each reviewer: - The brief is self-contained. A delegated reviewer gets only the brief, never your context. - The brief says read-only: inspect only, no writes, no git commands that change state. - For an `auto` or `inherit-parent` entry, omit the model so that reviewer runs on the parent model. If `delegate_task` rejects a configured entry, say so and run that reviewer on the closest available model of the same family from `orchestrator_capabilities`. Do not block the review on it. Read `references/reviewer-prompt.md` and fill in the template with: 1. The stated intent 2. The diff or file contents 3. The review rubric from `references/rubric.md` 4. The code-quality lens from `references/code-quality-review.md` The same filled template goes to all reviewers, so every model applies the code-quality lens. Drain results with `task_status`. ## Step 4, Synthesize As results come back, build a unified picture: 1. **Parse all findings** from the reviewers 2. **Identify consensus**. Findings raised by 2+ models independently are highest signal. 3. **Identify lone-model findings**. Still worth reading, but weight accordingly. 4. **Deduplicate**. Different models may describe the same issue differently. Merge these and note which models raised it. 5. **Note disagreements**. If one model flags something and another explicitly says the opposite, that's useful 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. Categorize every finding using these buckets: - **Act on**. Real issues affecting correctness, security, or maintainability given the actual goals. These would block a real PR. - **Consider**. Legitimate points, but you're not sure they outweigh the cost of addressing them right now. Worth the user's attention. - **Noted**. Technically valid but not actionable. Context-dependent, premature optimization, or low-impact given the current stage. - **Dismissed**. Wrong, nitpicky, or missing context. Brief explanation why. For each finding, include: - Which model(s) raised it - The category (act on / consider / noted / dismissed) - A one-line rationale for the categorization ## Output Format Present the verdict in this structure: ### Intent > [The stated intent paragraph from Step 2] ### Reviewers - Reviewer [label]: [model name], [N findings] (one bullet per reviewer) ### Act On [Findings that should be addressed. For each: description, which models raised it, why it matters.] ### Consider [Findings worth thinking about. For each: description, which models raised it, tradeoff involved.] ### Noted [Valid but low-priority. Brief list.] ### Dismissed [Rejected findings with brief rationale.] ### Agreement Map [Where did models agree, where did they diverge, and what does the pattern of agreement/disagreement tell us?] <!-- CORE-OVERLAY-START --> ## This repository (Asymmetric-al/core) Vendored from [p3-stack](https://github.com/uzairansaruzi/p3-stack) (MIT) at commit `09909eb`. Provenance is in `references/upstream.md`. On conflict, the current user request, root `AGENTS.md`, the nearest nested `AGENTS.md`, and the matching `docs/ai/rules/*` rulebook win over this skill. - Explicit invocation only: use it when the user invokes `/interrogate` (Claude Code, Cursor, T3 Code) or `$interrogate` (Codex), or when an invoked p3-stack skill routes here. Do not route other work to it. - The T3 Code tools named above map to Claude Code, Codex, and Cursor in `docs/ai/skills/p3-mode/references/core-adapter.md`. Read it before you delegate, watch a PR, schedule work, or drive a preview outside T3 Code. - Confirm before outward-facing or hard-to-reverse actions such as pushing, merging, deploying, deleting, or posting messages, unless the user authorized that action for this task. - For an explicit multi-provider council with scored rounds, use the `council` skill. Interrogate reviewers stay read-only and never auto-apply changes. Edit this canonical copy in `docs/ai/skills/interrogate/`, then run `bun run skills:sync` and `bun run skills:verify`. <!-- CORE-OVERLAY-END -->