interrogate

Spawns multiple LLM reviewers to adversarially review code changes and synthesize a verdict.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/mmdmcy/fluttAIrbar --skill interrogate-mmdmcy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interrogate
Source: https://github.com/mmdmcy/fluttAIrbar/tree/main/plugins/pstack/skills/interrogate
Command: npx skills add https://github.com/mmdmcy/fluttAIrbar --skill interrogate-mmdmcy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-reviewer code reviews miss blind spots and reflect one model's biases. This Skill runs adversarial multi-model reviews where independent LLM reviewers challenge the same diff, then synthesizes their findings into a prioritized verdict so real issues surface and noise gets filtered out. ## Core Features & Use Cases - Multi-Model Adversarial Review: Spawns one reviewer per configured model, each applying the same rubric and code-quality lens, so agreement across models signals high-confidence findings. - Lead Judgment Synthesis: Categorizes every finding as Act On, Consider, Noted, or Dismissed, with rationale, filtering nitpicks and hypothetical issues using full conversation context. - Structured Verdict Output: Produces an intent statement, reviewer summary, prioritized findings, and an agreement map showing where models converged or diverged. - Use Case: Before merging a feature branch, ask for an adversarial review of the diff; multiple models independently flag a race condition and a missing test, while style-only suggestions are dismissed with explanations. ## Quick Start Ask the assistant to interrogate the current branch diff and produce an adversarial multi-model review verdict.

Frequently Asked Questions about interrogate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a multi-model adversarial code review?▼

Point the skill at a diff, branch, or set of files and state the intent of the change. It spawns one reviewer per configured model with the same rubric, then synthesizes their findings into a single prioritized verdict.

What makes multi-model review better than a single reviewer?▼

Different models have different blind spots, priors, and reasoning patterns. Findings raised independently by two or more models are high-confidence signals, while lone-model findings are weighted lower during synthesis.

Can I configure which models act as reviewers?▼

Yes. Reviewer models come from the interrogate reviewers list in ~/.codex/pstack-models.md when present, otherwise default table entries are used. Unresolvable slugs fall back to the closest valid model without blocking the review.

Does the interrogate skill automatically apply code changes?▼

No. The deliverable is a synthesized verdict only. Findings are categorized as Act On, Consider, Noted, or Dismissed with rationale, and the user decides what to fix.

What kinds of issues does the review rubric cover?▼

The rubric covers correctness, root causes versus symptoms, structural integrity, verification and tests, complexity budget, and security. A separate code-quality lens targets structural simplification, file size growth, and spaghetti branching.