interrogate

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. Models differ in blind spots, priors, and reasoning patterns. Agreement across models is high-confidence signal; lone-model findings are worth reading but lower confidence. 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. What is this code trying to accomplish? Derive this from: Show more Installs 882 Repository cursor/plugins GitHub Stars 3.1K First Seen May 23, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Fail