interrogate

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

1|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/edivad1999/stuc-stack --skill interrogate-edivad1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interrogate
Source: https://github.com/edivad1999/stuc-stack/tree/main/skills/interrogate
Command: npx skills add https://github.com/edivad1999/stuc-stack --skill interrogate-edivad1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-reviewer code reviews miss blind spots and inflate nitpicks. This Skill runs adversarial multi-model review so independent LLM reviewers challenge a diff from different angles, then a lead judgment step filters noise into an actionable verdict. ## Core Features & Use Cases - Multi-Model Adversarial Review: Spawns one reviewer per configured model (Claude, GPT, Grok, etc.) with the same prompt, rubric, and code-quality lens so agreement across models signals high-confidence findings. - Structured Synthesis: Deduplicates findings, maps consensus and disagreement, and categorizes every item as Act On, Consider, Noted, or Dismissed with rationale. - Lead Judgment Filtering: Applies a pragmatic senior-engineer framework to reject hypothetical, nitpicky, or context-missing findings before presenting the verdict. - Use Case: Before merging a feature branch, run an adversarial review on git diff main...HEAD to catch correctness, security, and structural issues that a single reviewer would miss. ## Quick Start Ask the agent to interrogate the current branch changes and produce a synthesized adversarial 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 specific files, a diff, or a feature branch and it spawns one reviewer per configured model with the same prompt and rubric. Findings are synthesized into a verdict with Act On, Consider, Noted, and Dismissed categories.

What models are used for adversarial code review?▼

Reviewers default to claude-fable-5-1-thinking-max, gpt-5.6-sol-max, grok-4.6-fast-xhigh, and claude-opus-5-thinking-xhigh. A configured reviewer list in stuc-stack-models.mdc overrides the defaults, and unresolvable slugs fall back to the closest equivalent.

Does the interrogate skill auto-apply code changes?▼

No, the deliverable is a synthesized verdict only. The lead reviewer categorizes findings and explains rationale, but the user decides which Act On items to fix and can override any dismissed finding.

How does multi-model review handle false positives?▼

A lead judgment step filters findings using full conversation context, dismissing hypothetical issues, premature abstraction suggestions, and style preferences. Consensus across two or more models is treated as the highest-confidence signal.

When should I not use adversarial multi-model review?▼

It is overkill for trivial changes like typo fixes or single-line bug patches where spawning multiple reviewers adds cost without signal. It fits best for substantive diffs where correctness, security, or structural quality matters.