interrogate

# Interrogate On Codex, read the [platform mapping](../poteto-mode/references/codex-tools.md), including its per-skill notes, before following this skill. 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 `Agent` tool. Use the `interrogate reviewers` line in the `pstack-models.md` override sheet (`/setup-pstack` lists its path per runtime), one reviewer per entry, extending or shrinking the Reviewer A/B/C labels below to the configured entry count. If the sheet or that line is missing...