olibyte/jev-trader / .agents/skills/interrogate
interrogate
VerifiedUse 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.
Codex $interrogate. Claude Code, Cursor, and Antigravity /interrogate.
Interrogate
Spawn one reviewer per configured model to adversarially review code changes. The adversarial signal comes from model diversity, not assigned personas. The deliverable is a synthesized verdict. Do NOT auto-apply changes.
Step 1, 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 with any surrounding context files the reviewers need to understand the code.
Step 2, Intent
Before spawning reviewers, state the intent in one clear paragraph from the user's message, commit messages, the PR description if one exists, and the code. If you're unsure about the intent, ask the user before proceeding.
Step 3, Spawn Reviewers
Spawn all reviewers in one turn. Use the interrogate reviewers list from .agents/models.md when present, one reviewer per entry. If that file has no line, spawn 2 reviewers with no model and say they share the parent model.
Each reviewer is the host's general-purpose subagent, does not write to the parent workspace, and uses its configured interrogate reviewers entry. Omit model when that file has no line, or when the value is inherit, inherit-parent, or auto.
If a configured slug is rejected as unresolvable, check the valid slugs in the spawn error, pick the closest equivalent or omit model, and update .agents/models.md if that file named the bad slug. Do not block the review. Never treat inherit, inherit-parent, or auto as broken slugs.
Read references/reviewer-prompt.md and fill in the same template for every reviewer with the stated intent, the diff or file contents, the rubric from references/rubric.md, and the code-quality lens from references/code-quality-review.md.
Step 4, Synthesize
As results come back, build a unified picture. Parse every reviewer's findings. Merge findings that describe the same issue differently, and note which models raised each one. Findings two or more models raised independently are the highest signal. Read a lone model's finding, but weight it accordingly. Note disagreements. If one model flags something and another explicitly says the opposite, that is context for the verdict.
Step 5, Lead Judgment
You are the lead reviewer, a pragmatic senior engineer, not a neutral aggregator. Read references/lead-judgment.md for the full framework. Put every finding in one of four buckets, with the model(s) that raised it and a one-line rationale.
- Act on. Real issues affecting correctness, security, or maintainability given the actual goals. They would block a real PR.
- Consider. Legitimate, but you're not sure they outweigh the cost of addressing them now. Worth the user's attention.
- Noted. Technically valid but not actionable. Context-dependent, premature optimization, or low-impact at this stage.
- Dismissed. Wrong, nitpicky, or missing context, with a brief reason.
Output Format
Intent
[The stated intent paragraph from Step 2]
Reviewers
- Reviewer [label]: [model name], [N findings] (one bullet per reviewer)
Act On
[Each: description, which models raised it, why it matters.]
Consider
[Each: description, which models raised it, the tradeoff.]
Noted
[Brief list.]
Dismissed
[Each with a brief rationale.]
Agreement Map
[Where models agreed and diverged, and what that pattern tells us.]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |