// Code review checkpoint using codex review CLI. Returns structured result with pass/fail status and issues. Use when: 'code review', 'review changes', 'codex review', 'check my code'.
| name | reviewing-code |
| description | Code review checkpoint using codex review CLI. Returns structured result with pass/fail status and issues. Use when: 'code review', 'review changes', 'codex review', 'check my code'. |
| user-invocable | true |
Code review checkpoint that runs codex review on the current worktree.
Note: The gate-runner script runs this automatically for issues with gate:codex-review label. This skill documents the process for manual use.
# Review uncommitted changes
codex review --uncommitted --title "My Review"
# Review branch changes against main
codex review --base main --title "Feature Review"
# Review a specific commit
codex review --commit abc123
codex review (non-interactive, exits on completion)# Check for uncommitted changes
git status --porcelain
# Check for branch diff
git diff --quiet main...HEAD && echo "No branch changes" || echo "Has branch changes"
# For uncommitted changes
codex review --uncommitted --title "Checkpoint Review"
# For branch diff against main
codex review --base main --title "Checkpoint Review"
Codex review:
After reviewing, create a structured result:
{
"checkpoint": "codex-review",
"timestamp": "2026-01-19T12:00:00Z",
"passed": true,
"issues": [],
"summary": "No critical issues found"
}
Result Fields:
passed: true if no P1/P2 issues foundissues: array of {severity, message, file?, line?}summary: brief human-readable summarymkdir -p .checkpoints
cat > .checkpoints/codex-review.json << 'EOF'
{
"checkpoint": "codex-review",
"timestamp": "...",
"passed": true,
"issues": [],
"summary": "..."
}
EOF
Pass if:
Fail if:
$ codex review --uncommitted --title "Feature Review"
OpenAI Codex v0.87.0 (research preview)
--------
workdir: /home/user/project
model: gpt-5.2
...
[P2] Guard against missing script before execution — path/to/file.sh:45
Description of the issue...
[P3] Consider adding error handling — path/to/other.ts:120
Suggestion details...
The gate-runner.sh script runs codex review automatically:
./plugins/conductor/scripts/gate-runner.sh --issue ISSUE-ID --worktree /path/to/worktree
This:
gate:codex-reviewcodex review directly (no terminal spawn needed).checkpoints/codex-review.jsonReview code changes with parallel detection agents and smart fixing
Branch merging and conflict resolution patterns. Use when merging feature branches, handling conflicts, or cleaning up worktrees. Trigger with "merge branch", "resolve conflicts", "cleanup worktree".
Controls Chrome browser: takes screenshots, clicks buttons, fills forms, downloads images, inspects pages, captures network requests, checks console errors, debugs API issues. Use when: 'screenshot', 'click', 'fill form', 'download image', 'check browser', 'look at screen', 'capture page', 'check for errors', 'debug network', 'API failing', 'console errors'. Provides MCP tool discovery for 70 tabz_* browser automation tools.
Brainstorm ideas and design workflows with a beads expert. Use when: 'help me plan', 'how should I structure this', 'what beads features', 'brainstorm', 'before I create tasks', 'design my workflow'. For ideation BEFORE creating issues.
Docs/changelog checkpoint. Detects whether changes are user-facing and ensures documentation hygiene (CHANGELOG + lessons-learned) is handled or explicitly bypassed. Use when: 'docs check', 'changelog', 'release notes', 'did we update docs?'.
Multi-model conductor - spawns Haiku/Sonnet/Opus/Codex based on task complexity