run-codexlisted

# Run Codex (gpt-5.5) Use this skill when you want to hand a well-specified chunk of work to gpt-5.5 (via OpenAI's Codex CLI) instead of doing it inline — because it's bulk/mechanical, or because you want a second, independent perspective on something that ships. ## When to reach for Codex - **Bulk / mechanical work you can fully specify** — migrations, codemods, repetitive refactors, large data or log analysis. - **An independent review** — a second opinion on a diff or plan, from a different model than the one that wrote it. - **Not** for taste-critical UI/copy/API design, or vague tasks you can't pin down — those stay with the orchestrating model. Rule of thumb: **if you can fully specify the task in the prompt, it's a good Codex job.** If you can't specify it, don't delegate it. ## Commands ```bash # Investigate / review — read-only, cannot edit files: codex exec -s read-only "<self-contained prompt>" # Make edits — can modify the working tree: codex exec "<self-contained prompt>" # Review a diff — scope is required (bare `codex review` errors): codex review --base <branch> # or --uncommitted, or --commit <sha> ``` ## Write self-contained prompts Codex starts fresh — it does **not** see your conversation. Every prompt must carry its own context: the goal, the exact files/paths, the acceptance criteria, and any conventions that matter. **Codex reads `AGENTS.md`, not `CLAUDE.md`.** If the project's conventions live in `CLAUDE.md` (build/test commands