codex

# Codex Codex is an independent agent on PATH (`codex` — invoke as `command codex` if a shell alias shadows it), sharing this working tree and already authenticated. It is a second opinion, not ground truth: verify what it reports, own what it changes. It reads the same skills your repo carries. ## If `codex` is not installed When `codex` is missing from PATH, offer to install it — **ask the user for approval first**, never install on your own initiative. On yes, follow the current instructions at https://developers.openai.com/codex/cli. First-run authentication is interactive — hand that step to the user. Verify with `codex --version` before proceeding. ## Prompting Codex Prompt Codex like an operator, not a collaborator: compact, block-structured with XML tags. State the task, what "done" looks like, and the few constraints that matter. A tighter prompt beats a bigger run — improve the contract before raising `--effort`. - **One task per run.** Split unrelated asks (review, then fix, then docs) into separate runs; a mixed prompt gets a mixed result. - **Name skills instead of restating them.** Codex reads the same skills your repo carries — say "follow write-docs for the doc", "obey refactor-clean: no compatibility wrappers." Don't re-explain what a skill already carries. - **Blocks, added only where the task needs them:** - `<task>` — the concrete job, the repo/failure context, the expected end state. Nearly always present. - `<output_contract>` — exact...