Menu

Individual skill

interrogate

Adversarial multi-model review of a diff or branch. Several read-only reviewers, plus a security seat, try to break the change; you sort every finding into act on, consider, noted, or dismissed. Use for "interrogate this", "tear this apart", "stress-test my branch". Reports only, never fixes.

plugins/requie/endostack/skills/interrogate/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,537
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# interrogate

Several reviewers attack the same change independently, and you act as lead reviewer over what they return. The pressure comes from reviewers that think differently: different model families when the agent offers them, different briefs and stances when it does not. One extra seat always reviews from the attacker's side. You never edit code in this skill. The output is a verdict the user acts on.

Run it only when the user asks. Two cases belong elsewhere. If the user wants fixes applied, finish the verdict and let them choose what to act on. If the worry is what the change breaks outside its own lines, use the [`blast-radius` skill](../blast-radius/SKILL.md). Do not interrogate an abstract plan that has no code yet: reviewers of a plan invent risks because nothing constrains them. A prototype answers a design question better than a review panel does.

## Steps

Track a todo list with these six items: scope, intent, launch, merge, judge, report.

### 1. Scope

Pick what to review in this order, stopping at the first that applies: