interrogate

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

2|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/imjasonh/playground --skill interrogate-imjasonh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interrogate
Source: https://github.com/imjasonh/playground/tree/main/.cursor/skills/interrogate
Command: npx skills add https://github.com/imjasonh/playground --skill interrogate-imjasonh

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 the same change past several independent LLM reviewers and distills their findings into one prioritized, actionable verdict. ## Core Features & Use Cases - Multi-Model Adversarial Review: Spawns one reviewer per configured model, each applying the same prompt, rubric, and code-quality lens so the signal comes from model diversity. - Lead Judgment Synthesis: Deduplicates findings, flags consensus issues raised by 2+ models, and categorizes every finding as act on, consider, noted, or dismissed. - Configurable Reviewer Roster: Reads reviewer model assignments from a rules file with sensible defaults and graceful fallback when a model slug is unresolvable. - Use Case: Before merging a feature branch, ask for an adversarial review of the diff against main and receive a structured verdict listing what must be fixed, what to consider, and what was dismissed with rationale. ## Quick Start Ask the assistant to interrogate the current branch diff against main and produce a synthesized 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 get multiple AI models to review my code changes?▼

Multi-model review spawns one reviewer subagent per configured model, each receiving the same diff, rubric, and code-quality lens. Findings are then deduplicated and synthesized into a single verdict highlighting consensus issues raised independently by two or more models.

What is adversarial code review with LLMs?▼

Adversarial code review instructs each reviewer to stress-test the change rather than be encouraging, hunting for bugs, design flaws, security issues, and maintainability risks. A lead reviewer then filters the aggressive findings into act-on, consider, noted, and dismissed categories.

Can I configure which models participate in the review?▼

Yes, reviewer models are read from an interrogate reviewers list in the pstack-models rules file when present, with one reviewer per entry. Without configuration, a default table of four models is used, and unresolvable slugs fall back to the closest valid equivalent.

Does the multi-model review automatically apply fixes to my code?▼

No, the deliverable is a synthesized verdict only and changes are never auto-applied. The output lists findings by category with which models raised them and a rationale, leaving all remediation decisions to the user.

What happens when reviewers disagree or only find nitpicks?▼

Disagreements between models are surfaced in an agreement map as useful context for the verdict. If a reviewer's findings are all nits, the lead judgment framework treats that as a signal the code is probably fine and says so.