What problem does it solve? When Codex returns code changes as a patch or diff, applying them blindly risks introducing security flaws, unintended side effects, or out-of-scope edits. This Skill inserts a Claude approval layer between Codex output and your working tree so every patch is inspected before it touches your files. ## Core Features & Use Cases - Isolated Execution: Runs Codex inside a temporary git clone copy and captures changes with git diff, since Codex CLI has no --dry-run flag. - Structured Approval Checklist: Evaluates patches across Blocking (security), Analytical (correctness), and Advisory (scope) dimensions, with pass / modified-pass / reject decisions. - User Confirmation & Audit Trail: Shows a patch summary for gated changes and records the verdict in state.md for traceability. - Use Case: You route a refactoring task to Codex via the Codex-first Executor. Codex produces a diff touching three files; Claude reviews it, fixes a minor naming issue, presents the summary, and applies the patch only after your confirmation. ## Quick Start Ask Claude to run the Codex task in an isolated directory and approve the resulting patch before applying it to my repository.