verify

# Adversarial Verification Three agents with competing incentives: one finds issues, one disproves them, one judges. Before starting work, create a marker: `mkdir -p ~/.claude/tmp && echo "verify" > ~/.claude/tmp/heavy-skill-active && date -u +"%Y-%m-%dT%H:%M:%SZ" >> ~/.claude/tmp/heavy-skill-active` ## When to Use - Security-sensitive code (auth, crypto, permissions) - Data integrity (migrations, schema changes, ETL) - Financial logic (payments, billing, calculations) - Breaking changes (API contracts, public interfaces) ## The Three-Agent Pattern ### Agent 1: Finder ``` Agent(reviewer, "You are a bug finder. Analyze the following code/changes thoroughly. Score yourself: +1 for low-impact issues, +5 for medium-impact, +10 for critical. Report every potential issue you find — edge cases, race conditions, missing validation, security holes, logic errors, performance problems. Report your total score at the end. Target: [describe what to verify] Files: [list files]") ``` Finder over-reports by design — this is the **superset** of all possible issues. #### Cross-model finder (when the Codex bridge is available) All three agents here are Claude — one model family with shared blind spots, which is the exact self-preferential bias this skill exists to fight. When the Codex bridge is available, add a **non-Claude voice** to the panel by running, in parallel with Agent 1: ``` Agent(codex-verifier, "Independently find issues in the current diff. Report findings by severity...