codex-review · sateezg — Claude Code skill: code review and setup
codex-review is a Claude Code skill that asks OpenAI Codex to review code changes independently. It runs on requests to inspect a PR, branch, or module, and before a substantial commit or merge.
MIT ★ 195 updated 2026-08-10
/plugin marketplace add Sateezg/codex-bridge
/plugin install codex-bridge@codex-bridgeWhat codex-review does
codex-review sends a diff or project files to OpenAI Codex and returns findings grouped by severity, with file and line references. It can inspect uncommitted or staged changes, a branch against main, or a specific module. For a large change, Codex reads selected files instead of receiving one oversized diff.
The review runs in read-only mode, so Codex cannot alter the working tree. The skill calls for checking each finding and separating confirmed issues from disputed or unverified ones; it does not apply fixes automatically. It requires codex-run, Git, and Bash, and each review call uses the user's ChatGPT plan quota. Unrelated work should be committed or stashed first.
What it helps with
- review uncommitted changes before committing
- inspect a branch diff against
main - find security and error-handling issues in a PR
- get line-level findings for a specific module
Example prompts for the agent
- Review my uncommitted changes and group findings by severity.
- Check this branch against
mainbefore merging. - Review this PR and include a file and line for each finding.
How to install codex-review
1Plugin marketplace
/plugin marketplace add Sateezg/codex-bridge/plugin install codex-bridge@codex-bridgeThis installs the whole codex-bridge plugin with all its skills
2Manually: put the files in place
~/.claude/skills/codex-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/codex-review/
Manually: put the files in place
.agents/skills/codex-review/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/codex-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Sateezg/codex-bridge skills/codex-review2Manually: put the files in place
.github/skills/codex-review/SKILL.mdPlatform CLI
gemini skills install https://github.com/Sateezg/codex-bridge --path skills/codex-reviewManually: put the files in place
.devin/skills/codex-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about codex-review
How do I install codex-review in Claude Code?
Run /plugin marketplace add Sateezg/codex-bridge, then /plugin install codex-bridge@codex-bridge. The skill file is at ~/.claude/skills/codex-review/SKILL.md.
What does codex-review do?
It sends code changes to OpenAI Codex for an independent review and returns severity-grouped findings with file and line references. The review does not modify the working tree.
What does codex-review need to run?
It requires codex-run, Git, and Bash. Each review call uses ChatGPT plan quota.
Source text
SKILL.md · MIT
---
description: Get an independent code review from OpenAI Codex (GPT-5) on uncommitted changes, a branch diff, a PR, or a specific module — returns findings grouped by severity with file:line references. Use when the user says "review this", "review my changes", "check this PR", "what did I miss", or before they commit or merge something substantial.
---
# Code review by Codex
An independent reviewer that hasn't seen this conversation is genuinely useful:
it won't inherit your assumptions about the change. Use it as a *second* pass, not
a replacement for your own read.
## Pick the scope
```bash
git -C <repo> diff # uncommitted, unstaged
git -C <repo> diff --staged # staged
git -C <repo> diff main...HEAD # whole branch vs main
git -C <repo> diff --stat main...HEAD # size check first
```
Check the size before sending. Under ~1500 changed lines, pipe the diff in
directly. Larger than that, point Codex at the files instead and let it read
selectively — a giant pasted diff degrades the review.
## Run it
Small or medium change — pipe the diff as the prompt body:
```bash
{ echo "Review this diff as a senior engineer on this codebase. Report findings grouped by severity (Critical / Major / Minor / Nit). For each: file:line, what's wrong, and the concrete fix. Focus on correctness, security, error handling, race conditions, and missed edge cases. Skip style unless it hides a bug. If you find nothing at a severity level, say so rather than inventing findings."; echo; git -C <repo> diff main...HEAD; } | codex-run -C <repo> --timeout 1200 -
```
Large change or a whole module — let Codex read the tree itself:
```bash
codex-run -C <repo> --timeout 1800 \
"Review the changes on this branch versus main (run git diff main...HEAD yourself, and read the surrounding files for context). Report findings grouped by severity (Critical/Major/Minor/Nit) with file:line and a concrete fix for each. Prioritise correctness, security, error handling, and missed edge cases."
```
Both run read-only — Codex cannot modify the working tree.
## Handling the results
1. **Verify each finding before repeating it.** Open the cited file:line. Codex
reviews without conversation context and will sometimes flag intentional
behaviour, or cite a line that doesn't say what it claims. A review that
forwards false positives is worse than no review.
2. **Present it as three groups**: confirmed findings (with your verification),
findings you checked and disagree with (say why), and anything you couldn't
verify.
3. **Don't auto-fix.** Show the user the findings and let them choose. If they ask
for fixes, apply them yourself — you have the conversation context.
4. Attribute clearly: these are Codex's findings, and your assessment of them.
## Rules
- Bash timeout ≥ 1200000 ms (20 min) for anything branch-sized.
- Never pass `-s workspace-write` for a review.
- Ask the user to commit or stash unrelated work first, so the diff is clean.
- One review call per scope; spends the user's ChatGPT plan quota.
For a review that also needs follow-up investigation across the repo, use the
`codex-reviewer` subagent instead so the exploration stays out of this context.
© Sateezg · MIT · Sateezg/codex-bridge
Similar skills
All skills for Code review and refactoring →codex-review by other authors comes first.