codex-cli-review
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 / ⛔ Blocked
Verification
- 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 |
More from sd0xdev/sd0x-dev-flow
statusline-config
Customize Claude Code statusline. Use when: user says 'statusline', 'status line', 'customize statusline', 'modify statusline', 'statusline settings', 'statusline theme', 'change theme', 'color scheme', wants to add/remove/change segments (cost, git, model, context), switch color themes (catppuccin, dracula, nord), or asks what can be shown in the statusline.
52tech-spec
Tech spec generation and review. Use when: designing features, writing specs, spec review. Not for: requirements analysis (use req-analyze), implementation (use feature-dev), architecture advice (use codex-architect). Output: numbered tech spec document.
45codex-brainstorm
Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items.
7security-review
Security review via Codex MCP. Use when: OWASP Top 10 audit, dependency vulnerability check, security-sensitive changes. Not for: code review (use codex-code-review), test review (use test-review). Output: security findings + audit report.
7test-review
Test coverage review via Codex MCP. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
7post-dev-test
Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.
6