codex-review
Skill1 starsChanged 3 months agoMITView on GitHub
Use when you want an independent code review from a different model family: reviewing a diff before merging, self-reviewing a PR, or getting a second opinion on recent changes with the Codex CLI. Covers the codex review invocations that work, including the rule that a scope flag and a custom prompt cannot be combined.
- Reads credentials
94 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- Fondation-io/claude-skillstheir own version, first seen Nov 16, 2026
- saegim-works/claude-codex-bridgetheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- ryanportfolio/Harness-Firmwaretheir own version, first seen Nov 15, 2026
- thensls/nsls-personal-toolkittheir own version, first seen Nov 12, 2026
Used with
Projects with it also use addskill, apply-firmware and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
ryanportfolioSkillapply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions94 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 94
- ClickHouse/ClickHouse★ 51ksame name
- chaseai-yt/claudex-loop★ 3.2ksame name
- morethanwords/tweb★ 2.7ksame name
- alinaqi/maggy★ 711same name
- alinaqi/claude-bootstrap★ 708same name
- ThibautBaissac/rails_ai_agents★ 665same name
- ai-analyst-lab/ai-analyst★ 304same name
- Sateezg/codex-bridge★ 248same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
84 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- anger-translatorSkill
- cache-moneySkill
- codebase-memoirSkill
- goalpostSkill
- grand-tourSkill
- identity-theftSkill
- relocate-sessionSkill
- right-stuffSkill
- rubicon-wordpress-version-labSkill
- second-lookSkill
- secret-santa-generatorSkill
- showdownSkill
- star-chartSkill
- work-evidence-researchSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 81 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
All three scope flags reject a prompt: --base, --uncommitted, --commit.
- Very specific: line 73
Check with git check-ignore -q .reviews/codex/x.md: exit 0 means ignored, 1 means not ignored, and 128 means this is not a git repository …
- Very specific: line 78
Check the base branch exists: before --base: git rev-parse --verify main.
- Very specific: line 108
If review guidance genuinely must persist, the documented place is the repo's AGENTS.md, which Codex loads when a session starts (32 KiB by …
- Distinctive: line 116
Advisory only: Never auto-apply findings.
“Common” is measured: kept by at least 6 in 10 of the 81 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Codex Review
An independent review from a different model family. Value is author-bias: Codex sees what the model that wrote the code does not.
Preflight
which codex: if missing, tell the user to install it and stop. Then check that it can
authenticate. codex login status exits 1 with "Not logged in" when there is no saved login.
That does not always mean a review will fail: codex review also accepts the CODEX_API_KEY
environment variable, and a non-OpenAI model_provider in the user's config needs no
codex login. So if the status check fails, ask the user how they authenticate before
stopping, and do not work around a missing credential.
The constraint that breaks the obvious invocation
A scope flag and a custom prompt are mutually exclusive. Confirmed by running codex-cli 0.162.1; in the codex source, every release checked (a sample, not all) has the same rule.
$ echo "focus on X" | codex review --base main -
error: the argument '--base <BRANCH>' cannot be used with '[PROMPT]'All three scope flags reject a prompt: --base, --uncommitted, --commit. Only a bare
codex review <PROMPT>, with no scope flag, accepts one.
Some published review skills document cat prompt.md | codex review --base main -. That
form fails the same way.
Quick reference
| Goal | Command |
| Review a branch vs its base | codex review --base main |
| Review uncommitted work (staged, unstaged, untracked) | codex review --uncommitted |
| Review one commit | codex review --commit <sha> |
| Review a target you name | codex review "<what to review>" |
A bare prompt is the whole review request: the prompt itself is the target, and Codex is not
given a diff, so it must say what to review (for example "the changes on this branch since
main"). codex review with neither a flag nor a prompt exits with an error.
--title "<title>" works only with --commit: alone it exits 2, and with other forms it is
not used. It sets the commit title shown in the review summary. Run codex review --help
before assuming any other flag exists: this CLI changes.
Before the first run
- Ask before sending code out. Codex sends the diff, and anything else it reads or runs
while reviewing, to its configured model provider (OpenAI by default). Its default sandbox
can read files well beyond the repo, such as
.envfiles and anything under the home directory.--uncommittedalso includes untracked files that are not git-ignored, which can include stray secrets. Confirm with the user that this is acceptable for the repo. Do not rely on the sandbox to limit it: a read-only sandbox blocks writes and network access, not reads, and Codex's commands still run inside it. If a file must not leave the machine, do not run the review on that repo. - Know what it may do. Per the codex source, the review never stops to ask you.
The sandbox it runs in comes from the user's Codex configuration (
sandbox_mode, a permissions profile, project trust, or a-coverride), not from this skill. - Keep reports out of the review.
--uncommittedreviews untracked files, so an unignored report folder gets reviewed by the next run, including the report being written. Check withgit check-ignore -q .reviews/codex/x.md: exit 0 means ignored, 1 means not ignored, and 128 means this is not a git repository or something else failed. If it is not ignored, ask the user before adding.reviews/to.gitignore(or to.git/info/excludefor a local-only rule). If they decline, ask them for a directory outside the repo and use it wherever.reviews/codexappears below, or do not use--uncommitted. - Check the base branch exists before
--base:git rev-parse --verify main. If it fails, ask the user for the right base (for examplemasteror a release branch) and use that instead; codex does not stop on a missing base, it quietly switches to a different review prompt. When the remote branch is ahead of the local one, codex compares against the remote, so fetch first if that matters.
Use it
mkdir -p .reviews/codex
set -o pipefail
codex review --base main 2>&1 | tee ".reviews/codex/$(date +%Y-%m-%d-%H%M%S).md"pipefail keeps codex's exit status visible through tee. Reviews can take minutes on a
large diff, so in Claude Code start the command with run_in_background. The Bash tool's
timeout is 120 seconds by default and cannot be set above 10 minutes, so a timeout alone is
not a safe way to wait. When the background run finishes, read the saved report before
summarizing it.
Codex reads the repo itself and can run commands while it reviews. Treat every finding, and any claim it makes about the code (such as tests passing), as a claim to verify.
Don't reach for a custom prompt
The scope flags carry their own built-in review prompt, so choosing a scope means giving up your own instructions. That is a smaller loss than it looks: steering the reviewer with your own framing is how you get your own blind spots reflected back. Keep your reasoning out of any prompt you do write; the neutral review is the independent one.
If review guidance genuinely must persist, the documented place is the repo's AGENTS.md,
which Codex loads when a session starts (32 KiB by default, set by project_doc_max_bytes).
That a codex review run applies it is supported by the codex source but not confirmed in a
run, so check it on your repo before relying on it. It also applies to every codex
invocation in the repo, not just reviews, so decide it deliberately.
Rules
- Advisory only. Never auto-apply findings. Report them, then fix with approval.
- Report what Codex actually said, including findings you disagree with. Disagree in your own voice afterward; don't soften or omit.
- Save to
.reviews/codex/(or the directory the user chose instead), never inside.claude/, which holds agent configuration. - One report per run. The timestamp, to the second, keeps runs comparable and stops a rerun from overwriting the last report.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

