interrogate

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

4|1|Updated Dec 16, 2023
One-click install
npx skills add https://github.com/Shtian/AuthentiClash --skill interrogate-shtian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interrogate
Source: https://github.com/Shtian/AuthentiClash/tree/main/.claude/skills/interrogate
Command: npx skills add https://github.com/Shtian/AuthentiClash --skill interrogate-shtian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-perspective code reviews miss blind spots, and raw multi-reviewer output is noisy. This Skill runs adversarial reviews of a diff across multiple independent LLM models, then applies lead-reviewer judgment to filter findings into an actionable verdict. ## Core Features & Use Cases - Multi-Model Adversarial Review: Launches one reviewer per configured model (e.g., opus and sonnet) with the same prompt and rubric, so agreement across models is a high-confidence signal. - Structured Rubric and Quality Lens: Reviewers apply 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: Findings are deduplicated, consensus is identified, and every item is categorized as Act On, Consider, Noted, or Dismissed with rationale. - Use Case: Before merging a feature branch, ask for an adversarial review of git diff main...HEAD and receive a synthesized verdict listing only the issues that would block a real PR. ## Quick Start Ask the AI to interrogate the changes on your current feature branch 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 get an adversarial code review of my branch?▼

Point the Skill at your changes, such as a feature branch diff via git diff main...HEAD or specific files. It spawns one reviewer per configured model with the same rubric, then synthesizes their findings into a single categorized verdict.

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

Multi-model review sends the same prompt and rubric to different LLM models, such as opus and sonnet, so each reviews independently. Findings raised by two or more models are high-signal, while lone-model findings are weighted lower during synthesis.

Does the interrogate skill automatically apply code changes?▼

No. The deliverable is a synthesized verdict only, and reviewers are explicitly instructed not to modify files. You decide which Act On findings to address before shipping.

What kinds of issues does the review rubric cover?▼

The rubric covers correctness, root causes versus symptoms, structural integrity, verification, complexity budget, and security. A separate code-quality lens pushes for structural simplification, file-size discipline, and removal of spaghetti branching.

How are false positives from reviewers handled?▼

A lead-judgment step filters findings using conversation context, tracing call sites and dismissing hypothetical or preference-based findings. Rejected items appear in a Dismissed section with rationale so you can override the judgment.