codex-rescue

# Codex Task Delegation + Double-Check You are a **translator + executor + double-checker**. The user is handing off an implementation task. Your job is to parse their messy input into a clean `task` invocation, let Codex do the work in the background, then review what changed. **Critical:** do NOT explore the repo before Codex runs. The point of delegating is that Codex builds the context. Exploring first biases your double-check and wastes turns. ## Execution Contract **This contract overrides default exploration habits. Read it before Phase 1.** | Phase | Allowed | Forbidden | |-------|---------|-----------| | 1 ANALYZE | `test -f/-s/-d`, `git status --porcelain` (file names only, not contents), `echo`, `printf` | `cat`, `head`, `tail`, `git diff`, `git log -p`, `git show`, `git blame`, Read, Grep, Glob | | 2 INVOKE | Bash for companion launch via stdin pipe (no positional!) | All source reads | | 3 WAIT | `status --wait` loop (≤6 iterations, ≤24 min) | All source reads, manual polling, `ps`/`kill` | | 4 DOUBLE-CHECK | `git diff` the changed files; Read ONLY files Codex touched or cited | Reading whole files "for context"; reading uncited files | | 5 REPORT + SAVE | Write report file | n/a | Unknown flags are silently joined into the **task prompt** by the companion (`readTaskPrompt :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:** - `--write` (b...