interrogate

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-pass code review misses blind spots and reflects one reviewer's biases. This Skill runs the same diff through several independent LLM reviewers, then applies lead-reviewer judgment to filter noise, verify findings against the source, and produce a verdict you can act on before merging a PR. ## Core Features & Use Cases - Multi-model adversarial review: Spawns one reviewer per configured model with a shared prompt, rubric, code-quality lens, and blind-spot lenses, so consensus findings carry the highest signal. - Lead judgment synthesis: Deduplicates and verifies every finding against the actual code, then categorizes it as Act on, Consider, Noted, or Dismissed with rationale. - Pre-PR gate and external PR review: Serves as the gate before marking a PR ready, and converts findings into classified review comments (blocking/question/nit/praise) for another author's PR, posted only after explicit approval. - Use Case: Before opening a pull request, run an adversarial review of your branch diff to catch correctness bugs, structural regressions, and missing edge-case handling that a single reviewer would miss. ## Quick Start Ask the assistant to interrogate review the current branch diff before opening the pull request.

Frequently Asked Questions about interrogate

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

FAQPage Schema
How do I run an adversarial code review on a pull request?▼

Point the skill at a PR number, URL, or branch diff and it spawns one reviewer per configured model with the same prompt and rubric. Findings are deduplicated, verified against the source, and synthesized into a categorized verdict.

What is multi-model code review and why use it?▼

Multi-model review sends the same diff to several different LLMs so each challenges the code from an independent angle. Findings raised by two or more models independently are the highest-signal issues, while lone-model findings are weighted lower.

Can it review someone else's PR and post comments?▼

Yes. It converts verified findings into classified review comments (blocking, question, nit, praise) and drafts a full review. Nothing is posted to GitHub until the user explicitly approves, using gh pr review or the reviews API.

Does the review automatically apply fixes to my code?▼

No. The deliverable is a synthesized verdict only. The lead reviewer categorizes findings into Act on, Consider, Noted, and Dismissed buckets, but never auto-applies changes to the codebase.

What kinds of issues does adversarial review catch that normal review misses?▼

Blind-spot lenses target what a diff cannot show: missing parity with a reference implementation, unhandled states in a protocol or lifecycle matrix, and broken option interactions or resource cleanup paths.