adversarial-diff-verifylisted

# Skill: /adversarial-diff-verify [file] [builder claim] Read what the builder actually did, not what it said it did — a claim and a diff disagreeing is the single most common failure in parallel agent work, and it is invisible unless someone reads both. **Don't:** accept a claim because it is detailed and confident; the fabricated ones are the most detailed. **Don't** read only the diff — a diff shows what moved, not what the file now says, and claims about preservation are only checkable against the whole file. **Don't** return a verdict per file; return one per assertion, because builders are usually right about most of them and wrong about one. ## Inputs - `file` — the path the builder edited. - `builder claim` — its structured report. Typically JSON with fields like `changes[]`, `contentPreserved`, `buildPassed`, plus task-specific assertions. If either is missing, ask. Do not infer the claim from the diff — that defeats the check. ## Steps 1. **Read the file IN FULL.** Not a grep, not a range. Preservation claims are unfalsifiable without the whole text. 2. **Read the whole diff:** `cd <repo> && git diff -- <file>`. If the builder already committed, use `git show <sha> -- <file>`. 3. **Decompose the claim into assertions.** Each one gets its own verdict. A typical builder report yields 5–15. 4. **Test each assertion against the evidence**, in this order of suspicion: - **Preservation claims** ("kept verbatim: …") — check each named item is present *and unchang