Agent skill · writing content · cursor
interrogate
Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.
Why this skill is useful
Adds a structured multi-model review process that enhances code quality assessment beyond standard practices.
What it needs
About 3k tokens when loaded. Last updated 2026-08-06. 2,555 stars on the source repository.
What this skill does
Interrogate Spawn one reviewer per configured model to adversarially review code changes. Each model gets the same prompt and rubric. The adversarial signal comes from model diversity, not assigned personas. The deliverable is a synthesized verdict. Do NOT auto-apply changes. Step 1, Determine Scope Identify what to review from context: If the user points at specific files or a diff, use that If on a feature branch, run git diff main...HEAD (or the appropriate base branch) for the full changeset If the user's message references recent work, gather the relevant files Package the diff (or file contents) plus any surrounding context files the reviewers need to understand the code. Step 2, State the Intent Before spawning reviewers, state the intent explicitly. Derive this from: The user's message Commit messages PR description if one exists The code itself Write one clear paragraph. If you're unsure about the intent, ask the user before proceeding. Step 3, Spawn Reviewers Launch all reviewers in a single message using the Task tool. Use the interrogate reviewers line in ~/.cursor/rules/pstack-models.mdc, one reviewer per entry, extending or shrinking the Reviewer A/B labels below to the configured entry count. If the rule or that line is missing, use the table defaults. Subagent Default model ---------- --------------- Reviewer A claude-opus-5-5-xhigh Reviewer B grok-4.7-xhigh-fast For each reviewer: subagenttype: generalPurpose model: the configured interrogate reviewers entry, or the table default with no configured line. For an auto or inherit-parent entry, omit model so that reviewer runs on the parent model. readonly: true If the Task tool rejects a configured entry, run that reviewer on the table default of its family and say so. Families go by prefix: claude- and grok-. With no family match, use Reviewer A's default. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills cursor/interrogate