Interrogate

Read the pstack-t3 runtime before spawning workers, choosing models, scheduling, or isolating work. It maps those steps onto T3's orchestrator tools.

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.

The runtime's Modes section sets the mode lines of every brief this skill writes and how its spawns run in light mode.

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