verify-reviewlisted

# /verify-review ## Host dispatch contract - Codex: `$skill`, Codex collaboration roles, and GPT-5.6 tiers. - Claude: `/skill`, Agent/Skill tools, and Claude aliases. - A bare `/skill` in this shared source denotes the Claude form; Codex dispatches the same named skill as `$skill`. A review is a signal, not ground truth. Reviewers read stale code, invent line numbers, misread intent, and rubber-stamp. Verify the reviewer before spending budget acting on the verdict — in either direction: a wrong FIX_FIRST wastes a fix cycle; a wrong PASS ships a defect. Ported from the fable-agent-orchestration `review-verifier` skill (Apache-2.0). ## When to run - A review verdict arrived (review-gate, `codex review`, a PR review, a sub-agent critic) and you are about to merge, fix, or escalate based on it. - The base branch moved between when the review ran and now. - The verdict feels off — findings cite lines that don't match what you wrote. - Before telling Claude/Codex to "fix the review findings" — never forward a reviewer's claims to a fixer agent unverified; a fixer will happily "fix" code that was never broken. ## Procedure 1. **List the load-bearing claims.** The 1-3 findings that decide block-vs-pass. Ignore style nits for this pass. 2. **Open the cited files at CURRENT HEAD.** Not the diff the reviewer saw — the code as it exists now. `git log --oneline -3 -- <file>` tells you if it moved since the review. 3. **Pin the ref the claim was measured against.**