codex-cli-review
Skill192 starsChanged 36 days agoMITView on GitHub
Code review via Codex CLI with full disk access. Use when: deep review needing full codebase read, uncommitted change review. Not for: quick diff review (use codex-code-review), doc review (use doc-review). Output: severity-grouped findings + merge gate.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sd0xdev/sd0x-harnessword for word, first seen Oct 6, 2026
Other versions1 project uses a version of this.
Word for word · 1
- sd0xdev/sd0x-harness★ 192100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository102 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adrSkill
- agentctl-setupSkill
- architectureSkill
- askSkill
- best-practicesSkill
- bug-fixSkill
- bump-versionSkill
- check-coverageSkill
- claude-healthSkill
- code-exploreSkill
- code-investigateSkill
- codex-architectSkill
- codex-brainstormSkill
- codex-code-reviewSkill
- codex-explainSkill
- codex-implementSkill
- codex-review-branchSkill
- codex-review-docSkill
- codex-review-fastSkill
- codex-reviewSkill
- codex-securitySkill
- codex-setupSkill
- codex-test-genSkill
- codex-test-reviewSkill
- contract-decodeSkill
- create-prSkill
- create-requestSkill
- de-ai-flavorSkill
- debugSkill
- deep-analyzeSkill
- deep-exploreSkill
- deep-researchSkill
- dep-auditSkill
- deploy-flowSkill
- dev-security-auditSkill
- doc-refactorSkill
- doc-reviewSkill
- epic-mergeSkill
- feasibility-studySkill
- feature-devSkill
- feature-verifySkill
- fp-briefSkill
- generate-runnerSkill
- gh-stackSkill
- git-investigateSkill
- git-profileSkill
- install-hooksSkill
- install-rulesSkill
- install-scriptsSkill
- issue-analyzeSkill
- jiraSkill
- load-pr-reviewSkill
- merge-prepSkill
- necessity-auditSkill
- next-stepSkill
- obsidian-cliSkill
- op-sessionSkill
- orchestrateSkill
- plan-reviewSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Don't need MCP's context persistence feature
- Very specific: line 24
Only want to see diff without waiting for Codex exploration (use /codex-review-fast)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Codex CLI Review Skill
Trigger
- Keywords: codex cli review, cli review, script review
When to Use
- Need Codex to independently explore the entire project (full disk read)
- Don't need MCP's context persistence feature
- Want to use Codex CLI's native review format
When NOT to Use
- Need iterative review (use
/codex-review-fast --continue) - Need to follow up with Codex (use MCP version)
- Only want to see diff without waiting for Codex exploration (use
/codex-review-fast)
Difference from MCP Version
| Feature | CLI Version (this skill) | MCP Version |
| Independent explore | Full disk read | Needs explicit instruction |
| Context persistence | None | threadId |
| Iterative review | Each run independent | --continue |
| Format | Codex native format | Custom prompt format |
| Execution method | Script invocation | MCP tool invocation |
Workflow
┌─────────────────────────────────────────────────────────────────┐
│ Step 1: Check Changes │
├─────────────────────────────────────────────────────────────────┤
│ git status --porcelain │
│ No changes -> Early exit │
└─────────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────────┐
│ Step 2: Execute Codex CLI │
├─────────────────────────────────────────────────────────────────┤
│ codex review --uncommitted │
│ -c 'sandbox_permissions=["disk-full-read-access"]' │
│ │
│ Codex will independently: │
│ - Read changed files │
│ - Explore related dependencies │
│ - Check existing tests │
│ - Understand project structure │
└─────────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────────┐
│ Step 3: Output Review Results │
├─────────────────────────────────────────────────────────────────┤
│ Codex native format: │
│ - Summary │
│ - Issues (Critical/Major/Minor/Suggestion) │
│ - Recommendations │
└─────────────────────────────────────────────────────────────────┘Script
bash skills/codex-cli-review/scripts/review.sh [options]Options
| Parameter | Description |
--base <branch> | Compare with specified branch |
--title "<text>" | Set review title |
--prompt "<text>" | Custom review instructions |
I/O Contract
Input:
- Git working directory with changes
Output:
- Codex review report (stdout)
- Exit code: 0 = success, non-0 = failure
Output
## Codex CLI Review Report
### Findings
#### P0/P1/P2
- [file:line] Issue → Fix recommendation
### Merge Gate
✅ Ready / ⛔ BlockedVerification
- Script executes without errors
- Codex explored the project (file references visible in output)
- Output includes issue classification
Examples
# Review uncommitted changes
/codex-cli-review
# Compare with main branch
/codex-cli-review --base main
# With title
/codex-cli-review --title "Feature: User Auth"
# Custom review instructions
/codex-cli-review --prompt "Focus on security and performance"Related
| Command/Skill | Difference |
/codex-review-fast | MCP version, supports iterative review |
/codex-review | MCP version, includes lint + build |
/codex-review-branch | MCP version, reviews entire branch |
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.

