# Codex Review

Run an independent code review using the OpenAI Codex CLI in headless mode.

- Repository: https://github.com/jezweb/claude-skills (1094 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-09
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add jezweb/claude-skills --skill codex-review -g -a claude-code -y`
Codex: `npx skills add jezweb/claude-skills --skill codex-review -g -a codex -y`
Cursor: `npx skills add jezweb/claude-skills --skill codex-review -g -a cursor -y`
Gemini CLI: `npx skills add jezweb/claude-skills --skill codex-review -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add jezweb/claude-skills`

## Description

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'.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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 not logged in. If that happens, instruct the user to run `codex login` and stop.

## Determine scope

Pick the scope flag based on what the user asked for:

| User intent | Flag |
|---|---|
| "codex review" / "review the app" / "full review" / default | no flag (reviews whole app at current HEAD) |
| "review my changes" / "review what I just did" / "review uncommitted" | `--uncommitted` |
| "review this branch vs main" / "review the PR" | `--base main` (or the branch they name) |
| "review commit abc123" | `--commit abc123` |

**Default is whole-app review.** A bare "codex review" with no qualifier means review the entire codebase at HEAD, not just uncommitted changes. Only use `--uncommitted` if the user specifically refers to their recent/uncommitted work.

The rest: https://github.com/jezweb/claude-skills/blob/HEAD/plugins/dev-tools/skills/codex-review/SKILL.md