interrogate

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

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jeremybrasher/grokbot-skills --skill interrogate-jeremybrasher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interrogate
Source: https://github.com/jeremybrasher/grokbot-skills/tree/main/collections/pstack/skills/interrogate
Command: npx skills add https://github.com/jeremybrasher/grokbot-skills --skill interrogate-jeremybrasher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-reviewer code reviews miss blind spots and inherit one model's biases. This Skill runs adversarial multi-model review so independent LLM reviewers challenge a diff from different angles, then synthesizes their findings into one categorized verdict. ## Core Features & Use Cases - Multi-Model Review: Spawns one read-only reviewer per configured model, each applying the same prompt, rubric, and code-quality lens to the same diff. - Lead Judgment Synthesis: Deduplicates findings, maps cross-model agreement, and buckets every item as act on, consider, noted, or dismissed with rationale. - Guardrails: Holds when scope, intent, or reviewer list is missing, never auto-applies patches, and falls back to valid model slugs when a configured slug fails. - Use Case: Before merging a feature branch, run an adversarial review over git diff main...HEAD to surface correctness, security, and maintainability issues that a single reviewer would miss. ## Quick Start Ask the agent to interrogate the current branch diff against main and return a synthesized verdict with act-on, consider, noted, and dismissed findings.

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 code review on a git diff?▼

Point the skill at specific files, a diff, or a feature branch; it runs git diff against the base branch for the full changeset. It then spawns one read-only reviewer per configured model and synthesizes their findings into a single verdict.

What is adversarial code review with multiple LLMs?▼

Adversarial multi-model review sends the same prompt, rubric, and code-quality lens to several different models so each challenges the change independently. Findings raised by two or more models are treated as the highest-signal issues.

Which models does the interrogate skill use as reviewers?▼

It reads a configured reviewer list from ~/.cursor/rules/pstack-models.mdc when present, otherwise it uses default slugs such as claude-fable, gpt, grok, and claude-opus variants. If a slug is unresolvable, it falls back to the closest valid model of the same family.

Does the interrogate skill auto-apply fixes to my code?▼

No, the deliverable is a verdict only. Reviewers run read-only, findings are categorized as act on, consider, noted, or dismissed, and no patches or fix PRs are created unless you explicitly ask afterward.

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

Skip it when you want fixes auto-applied, when there is no diff, file, or branch scope to review, or when the intent of the change cannot be stated and the user is unavailable to clarify.