interrogate

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

136|8|Updated May 9, 2026
One-click install
npx skills add https://github.com/Sma1lboy/rove --skill interrogate-sma1lboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interrogate
Source: https://github.com/Sma1lboy/rove/tree/main/.agents/skills/pstack/skills/interrogate
Command: npx skills add https://github.com/Sma1lboy/rove --skill interrogate-sma1lboy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-reviewer code reviews carry one model's blind spots and biases, making it easy to miss bugs, design flaws, and maintainability risks in a changeset. ## Core Features & Use Cases - Multi-Model Adversarial Review: Spawns one reviewer per configured model so independent models challenge the same diff from different angles, turning cross-model agreement into high-confidence signal. - Structured Rubric and Quality Lens: Each reviewer applies a shared rubric covering correctness, root causes, structural integrity, verification, complexity, and security, plus a strict code-quality lens targeting structural simplification. - Lead Judgment Synthesis: A lead-reviewer step filters findings into Act On, Consider, Noted, and Dismissed buckets, deduplicates across models, and produces an agreement map. - Use Case: Before merging a feature branch, run an adversarial review on the full diff so several models independently hunt for bugs and design flaws, then receive a single prioritized verdict instead of four raw review dumps. ## Quick Start Ask the agent to interrogate the current branch changes against main 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 on my branch?▼

Point the skill at your changes, such as a git diff against the base branch, and it spawns one reviewer per configured model with the same prompt and rubric. It then synthesizes all findings into a single categorized verdict.

What does the interrogate skill review in a code change?▼

Reviewers apply a rubric covering correctness, root causes versus symptoms, structural integrity, verification, complexity budget, and security. A code-quality lens additionally pushes for structural simplification and flags spaghetti growth and file-size regressions.

Does the adversarial review automatically apply fixes to my code?▼

No. The deliverable is a synthesized verdict only, with findings categorized as Act On, Consider, Noted, or Dismissed. The skill explicitly does not auto-apply changes; you decide what to fix.

What happens if a configured reviewer model slug is invalid?▼

The skill checks the valid slugs in the tool's error message, picks the closest equivalent in the same model family, and continues the review. It does not block on the slug issue and suggests updating the configured value separately.

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

It is overkill for trivial changes like typo fixes or single-line edits where one reviewer suffices. The workflow spawns multiple subagents and reads several reference files, so it suits substantive changesets where review depth justifies the cost.