Menu
Use Codex CLI (not MCP) to review uncommitted changes. Codex explores the codebase independently with full disk read access.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | codex-cli-review |
| description | Use Codex CLI (not MCP) to review uncommitted changes. Codex explores the codebase independently with full disk read access. |
| allowed-tools | Bash(bash:*), Read, Grep, Glob |
| context | fork |
/codex-review-fast --continue)/codex-review-fast)| 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 |
┌─────────────────────────────────────────────────────────────────┐
│ 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 │
└─────────────────────────────────────────────────────────────────┘
bash skills/codex-cli-review/scripts/review.sh [options]
| Parameter | Description |
|---|---|
--base <branch> | Compare with specified branch |
--title "<text>" | Set review title |
--prompt "<text>" | Custom review instructions |
Input:
Output:
# 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"
| 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 |
Document codebase as-is via parallel sub-agents. Use when researching how code works, mapping architecture, or answering questions about existing systems. Auto-detects thoughts/ directory — if present, integrates historical context and syncs; if absent, skips those steps.
Create the Questions artifact before codebase research, design, planning, or implementation. Use for feature tickets, architecture changes, unclear code work, CRISPY/QRSPI Questions phase, or when the agent needs to define code-answerable unknowns and human questions before researching or planning.
Create a concise Design Concept artifact after questions and codebase research are available. Use for CRISPY/QRSPI Design phase, architecture alignment, feature design discussion, or turning current-state research into a small human-reviewable proposed shape before detailed planning.
Create an interface-first Structure Outline before detailed planning or implementation. Use for CRISPY/QRSPI Structure Outline phase, vertical planning, method signatures, type contracts, API/component boundaries, or converting an accepted design concept into end-to-end slices with verification checkpoints.
Create comprehensive handoff documents for transferring work to another agent session. Use when the user requests to create a handoff, end a session, or document work-in-progress for future continuation.
Create detailed implementation plans through interactive research and iteration. Use when starting a new feature or ticket that needs a comprehensive technical plan. Saves plans to the repo-appropriate plans location and emits Personal Knowledge events when applicable.