codex-review
Run an independent code review using the OpenAI Codex CLI in headless mode. Gets a second opinion from a different model family (the current Codex models) on recent changes, a PR, a commit, or the whole app — covering bugs, regressions, security, data consistency, UX/state bugs, performance risks, and testing gaps. Saves a severity-prioritised report to .jez/reviews/. Triggers: 'codex review', 'review with codex', 'independent code review', 'what does codex think', 'get codex to review'.
npx skills add jezweb/claude-skills --skill codex-review --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Codex Review Run an independent code review via the OpenAI Codex CLI (`codex review`). The value is a second opinion from a **different model family** than the one that wrote the code — Codex catches things Claude misses due to author bias. Complements `brains-trust` (generic multi-model opinions). This skill is specialised: git-aware, uses a tuned review prompt, saves structured output. ## When to Use - After a meaningful change, before committing or shipping - Before opening a PR, to self-review with an independent reviewer - When something feels off but you can't articulate what - Periodic whole-app reviews for projects in active development - When the user explicitly asks for an "independent" or "second opinion" review **Do NOT use** for: - Trivial changes (typos, one-line fixes) - Research questions or architecture discussions — use `brains-trust` instead - Auto-fixing issues — this is advisory only ## Preflight 1. Confirm Codex CLI is installed: ```bash which codex ``` If missing: tell the user to install it (`brew install codex` on macOS, or see https://github.com/openai/codex) and stop. Do not continue. 2. Confirm auth: the first `codex review` call will fail clearly if n
- When to Use
- Preflight
- Determine scope
- Run the review
- Summarise for the user
- Rules
- Verification
which codex
mkdir -p .jez/reviews
cat "${SKILL_DIR}/prompt.md" | codex review --uncommitted - 2>&1 | tee "$OUT"
Vs base branch
cat prompt.md | codex review --base main - 2>&1 | tee "$OUT"
Specific commit
cat prompt.md | codex review --commit abc123 - 2>&1 | tee "$OUT"
Current HEAD (no scope flag)
cat prompt.md | codex review - 2>&1 | tee "$OUT"What does the codex-review skill do?
Run an independent code review using the OpenAI Codex CLI in headless mode. Gets a second opinion from a different model family (the current Codex models) on recent changes, a PR, a commit, or the whole app — covering bugs, regressions, security, data consistency, UX/state bugs, performance risks, and testing gaps. Saves a severity-prioritised report to .jez/reviews/. Triggers: 'codex review', 'review with codex', 'independent code review', 'what does codex think', 'get codex to review'.
How do I install it?
Run `npx skills add jezweb/claude-skills --skill codex-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jezweb/claude-skills, a repository with 954 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.