codex-verifylisted

# Codex Claim Verification Prove or disprove what the assistant agent claims to have done in the current turn, independently. This is a **trust check**, not an issue hunt — separate from `/codex-review`. ## Why this is separate from `/codex-review` - `/codex-review` looks for new bugs in the diff (issue hunt). - `/codex-verify` proves the assistant's claims against actual state (trust verification). A single tool would dilute both contracts. The verifier is **structurally narrowed by design**: it does not propose fixes, does not list issues outside the assistant's claims, does not drift into "while I'm here let me also...". That narrowness is the feature — it forces every "verified" verdict to be backed by a deterministic tool output. The two skills compose. Run both when you want both questions answered. Do not merge their outputs. ## Instructions ### Phase 1: Gather inputs 1. Combine the diff: - `git diff` (unstaged changes) - `git diff --cached` (staged changes) 2. **If the diff is empty**, stop and tell the user "no changes to verify." 3. Capture the assistant's last message — the message in the prior turn where the assistant stated what it did. This is the source of claims to verify. Pass it through verbatim — do not summarize, do not paraphrase. The agent decomposes claims directly from this text. If the conversation has no prior assistant message stating what was done (e.g., the diff exists but came from a manual edit), tell the user: "no assistant claim