Codex Review
Run an independent code review using the OpenAI Codex CLI in headless mode.
Install
npx skills add jezweb/claude-skills --skill codex-review -g -a claude-code -y- Repository
- jezweb/claude-skills1.1k
- Category
- Design
- Updated
- 26d ago
- License
- MIT
- Context cost
- Lightabout 1,061 tokens
- Runs scripts
- No, instructions only
What it does
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'.
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-trustinstead - Auto-fixing issues, this is advisory only
Preflight
-
Confirm Codex CLI is installed:
which codexIf missing: tell the user to install it (
brew install codexon macOS, or see https://github.com/openai/codex) and stop. Do not continue. -
Confirm auth: the first
codex reviewcall will fail clearly if not logged in. If that happens, instruct the user to runcodex loginand 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.
