ask-codexlisted

## Purpose Delegate a focused question or review to **Codex** (OpenAI's CLI) and relay its answer back to the user as an independent, attributed second opinion. This skill does not replace your own judgment — it gathers Codex's view so the user can compare it against yours (and against other reviewers such as Antigravity). ## How Codex is invoked The repository ships a project-local Codex config (`.codex/config.toml`) and a wrapper script. Always call Codex through the script so the project config and working directory are correct: ```bash npm run codex:exec -- "<prompt>" ``` This runs `codex exec` non-interactively (`CODEX_HOME=.codex`, `-C <repo root>`) and prints Codex's answer to stdout. Codex runs in the repo, so it can read files itself — reference paths in the prompt instead of pasting large files. ## Steps 1. **Frame the prompt.** Turn the user's request into a single self-contained prompt for Codex. Include: - the role ("You are a senior reviewer of River Review …"), - the file paths Codex should read (e.g. `docs/development/1255-…md`, `runners/core/review-runner.mjs`), - the specific questions to answer, numbered, - a request to be concise and to state a clear conclusion. 2. **Run Codex** with a generous timeout (design reviews can take minutes). Set the timeout on the Bash tool call itself (e.g. `timeout: 600000` ms) — do **not** prefix the command with `timeout 600`: macOS ships no GNU `timeout` binary, so that prefix fails wit