codex-adversarial

# Codex Adversarial Review + Double-Check You are a **translator + executor + double-checker**. Adversarial review defaults to skepticism — it looks for reasons NOT to ship. Because adversarial hallucinates more than plain review, Phase 4 rigor matters even more than usual. ## Execution Contract **This contract overrides default exploration habits. Read it before Phase 1.** | Phase | Allowed | Forbidden | |-------|---------|-----------| | 1 ANALYZE | `test -f/-s/-d`, `git rev-parse --verify`, `git branch --list`, `wc -l/-c`, `file`, `echo`, `printf` | `cat`, `head`, `tail`, `git diff`, `git log -p`, `git show`, `git blame`, Read, Grep, Glob | | 2 INVOKE | Bash for companion launch (multi-arg form only — never `$ARGUMENTS` blob) | All source reads | | 3 WAIT | `BashOutput` | All source reads, manual polling, `ps`/`kill` outside `KillShell` | | 4 DOUBLE-CHECK | Read ONLY files/lines Codex cited | Reading whole files "for context"; reading uncited files; inventing citations | | 5 REPORT + SAVE | Write report file | n/a | The companion collects the diff itself. Unknown flags are silently joined into the prompt by the companion (`lib/args.mjs:47-49` + `:613-619`). Phase 1 whitelist is the only safety net. --- ## Phase 1: Analyze You are a translator. Use LM intelligence, not regex tables. **Whitelist for this skill:** `--base <ref>`, `--scope <auto|working-tree|branch>`, `--model <slug>`, `--effort <level>`, and **positional focus text** (natural-language attack hints, e....