Use when the user wants a local second-opinion code review via OpenAI Codex CLI — on the current branch, staged changes, a single file, or a piped diff. Triggers include "codex review", "review with codex", "run codex on this diff", "second opinion from codex", or pre-commit / pre-PR review requests that ask for codex specifically.
90
97%
Does it follow best practices?
Impact
97%
2.25xAverage score across 2 eval scenarios
Passed
No known issues
Your team has just shipped a major sprint that touched both the backend API layer and the React frontend. The branch has accumulated changes across roughly 50 files — new API routes, updated React pages, revised database migrations, and refactored shared utilities. A senior engineer wants a Codex CLI review before the PR is opened, but experience has shown that throwing the entire diff at Codex at once produces shallow, low-quality output.
Your task is to script the review process so that the diff is reviewed in logical slices rather than all at once, making each Codex invocation focused enough to produce useful findings.
Write a shell script named review.sh that performs the review in multiple passes. The script should:
Assume:
feature/sprint-42 and the base is main..claude/skills/codex-review/resources/PROMPT.md file is present in the current working directory.