← ClaudeAtlas

interrogatelisted

Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "second opinion", "second look", "2nd opinion", "what could this break", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles; only findings a run proves survive.
RIJUDEVx/agent-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill RIJUDEVx/agent-skills
# 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. A finding survives only when a run proves it. 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, one per slot, with the harness's sub-agent tool or `delegate_task`. Aim for **model diversity**: different model families catch different bugs. In T3 Code, pick 3-4 strong models from the user's favourites, from different families, and start each with `delegate_task` (the `t3-tools` skill has the steps). Elsewhere, choose 3-4 distinct high-capability models the harness exposes. If you