codex-review
Skill665 starsChanged 6 months agoMITView on GitHub
Get an independent second opinion from OpenAI Codex CLI on a plan, diff, spec, or Claude's last response. Use when the user asks to "get a second opinion", "have codex review", "cross-check with codex", or wants adversarial review of Claude's output. Argument is one of plan|diff|spec|last-response (default last-response).
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
- ai-analyst-lab/ai-analyst★ 304same name
- Sateezg/codex-bridge★ 248same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- ncklrs/startup-os-skills★ 51same 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 repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude_37signals/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- accessibility-reviewSkill
- action-cable-patternsSkill
- active-storage-setupSkill
- api-versioningSkill
- authentication-flowSkill
- behavioral-guidelinesSkill
- caching-strategiesSkill
- code-reviewSkill
- dependabot-reviewSkill
- extraction-timingSkill
- friction-reviewSkill
- i18n-patternsSkill
- mutation-testingSkill
- performance-optimizationSkill
- postgres-patternsSkill
- rails-architectureSkill
- rails-concernSkill
- security-auditSkill
- solid-queue-setupSkill
- accessibility-reviewSkill
- action-cable-patternsSkill
- active-storage-setupSkill
- api-versioningSkill
- authentication-flowSkill
- behavioral-guidelinesSkill
- caching-strategiesSkill
- code-reviewSkill
- codex-reviewSkill
- dependabot-reviewSkill
- extraction-timingSkill
- friction-reviewSkill
- i18n-patternsSkill
- mutation-testingSkill
- performance-optimizationSkill
- postgres-patternsSkill
- rails-architectureSkill
- rails-concernSkill
- security-auditSkill
- solid-queue-setupSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 81 edited versions we read keep these.
4
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
- Distinctive: line 22
Never fall back to reviewing Claude's own output if Codex fails.
- Distinctive: line 26
Run in order. Stop cleanly on first failure:
- Very specific: line 36
plan: if there is an active in-conversation plan, write it to a temp file as above. - Very specific: line 38
diff: no file needed — Codex reads the repo directly via codex review --uncommitted. - Very specific: line 60
Use a single Bash call with 600000ms timeout.
- Distinctive: line 93
Stop after emitting failure.
- Distinctive: line 97
After a successful review, end your turn with one question to the user:
- Very specific: line 101
Only if the user says yes, produce a ### Reconciliation section with three bullet lists: Adopt, Reject (each with a one-line reason), Defer …
“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 — Independent second opinion from Codex CLI
Argument: $ARGUMENTS — one of plan | diff | spec | last-response. Default last-response.
Never fall back to reviewing Claude's own output if Codex fails. If Codex can't run, say so and stop.
1. Preflight
Run in order. Stop cleanly on first failure:
command -v codex >/dev/null 2>&1 || { echo "codex CLI not found. Install: https://github.com/openai/codex"; exit 0; }
codex login status 2>&1 | grep -qi "logged in" || { echo "codex not logged in. Run: codex login"; exit 0; }2. Resolve target
last-response(default): identify your previous substantive assistant turn (the last turn with user-facing prose — skip turns that are pure tool calls or tool results). Write that prose verbatim to a temp file via the Write tool:$(mktemp -t codex-review).md. Record the path as$TARGET_FILE.plan: if there is an active in-conversation plan, write it to a temp file as above. Otherwise pick the newest file under./.claude/plans/(ls -t ./.claude/plans/*.md 2>/dev/null | head -1). If neither exists, report "no plan found" and stop.spec: pick the newestspec.mdunder./specs/(fd -t f 'spec\.md$' ./specs 2>/dev/null | xargs ls -t 2>/dev/null | head -1). If none, stop.diff: no file needed — Codex reads the repo directly viacodex review --uncommitted.
3. Build rubric (skip for diff)
The diff target uses codex review's built-in review prompt — do not pass a custom rubric there (--uncommitted is mutually exclusive with [PROMPT] and will error).
For plan | spec | last-response, write this rubric to $(mktemp -t codex-rubric).txt:
You are an adversarial reviewer giving a second opinion. Be terse. Do not restate what is correct.
Check, in order:
1. Correctness — logic errors, off-by-one, wrong APIs, broken invariants.
2. Missing edge cases — nulls, empty inputs, concurrent writes, partial failures, auth gaps.
3. Simpler alternatives — is there a shorter, more conventional, or better-supported approach?
4. Risk — blast radius, reversibility, data loss, security implications.
Output format: 4 sections with those exact headings. Skip a section if you have nothing material. No preamble, no summary, no praise.4. Invoke Codex
Use a single Bash call with 600000ms timeout. Capture stdout and exit code. Do not pass -c model=... — rely on the user's ~/.codex/config.toml defaults.
diff:codex review --uncommittedplan|spec|last-response:{ printf '=== CONTENT TO REVIEW ===\n'; cat "$TARGET_FILE"; printf '\n\n=== REVIEW INSTRUCTIONS ===\n'; cat "$RUBRIC_FILE"; } \ | codex exec --sandbox read-only --skip-git-repo-check -
Pass all content via stdin. Never put file contents on argv.
5. Emit review
On exit code 0:
### Codex Review
<codex stdout verbatim — no edits, no paraphrase>On non-zero exit or timeout:
### Codex Review (FAILED)
Codex exited with status <N>. Stderr tail:
<last 20 lines of stderr>Stop after emitting failure. Do not substitute your own review.
6. Ask before reconciling
After a successful review, end your turn with one question to the user:
Want me to reconcile — decide which points to adopt, reject, or defer?
Only if the user says yes, produce a ### Reconciliation section with three bullet lists: Adopt, Reject (each with a one-line reason), Defer (each with a one-line reason to revisit later). Do not rubber-stamp Codex; reject points that are wrong or off-scope.
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.

