review
Ask Codex to review local git changes (uncommitted, against a base branch, or a commit), optionally with a focus. Use for "/codex-bridge:review".
Source facts
- Repository
- collisionengineers/claude-using-codex-skill
- Last source activity
- September 3, 2026 at 15:39
- Detected SKILL.md language
- English
- Stars
- 0
- Forks
- 0
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- review
- description
- Ask Codex to review local git changes (uncommitted, against a base branch, or a commit), optionally with a focus. Use for "/codex-bridge:review".
- argument-hint
- [--base <branch> | --commit <sha>] [--focus "<text>" | <trailing focus text>] [--bg]
- disable-model-invocation
- true
- allowed-tools
- Bash(node:*), Bash(git:*), Read, AskUserQuestion
Run a Codex code review and present the findings without acting on them.
## Steps
1. Parse `$ARGUMENTS`: `--base <branch>`, `--commit <sha>`, `--focus "<text>"` (or any trailing free text as focus), `--bg`. Default scope is uncommitted changes.
2. Size the diff first: `git diff --shortstat` and `git status --short`. If more than about 15 files or 1500 changed lines and `--bg` was not given, use AskUserQuestion once to offer background execution, since native review of large diffs can take several minutes.
3. Run:
```
node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-bridge.mjs" review [--base B | --commit SHA] [--focus "<text>"]
```
Without `--focus` this is Codex's native reviewer. With `--focus` it becomes a targeted review turn using the review template. Use `run_in_background: true` for `--bg` or large diffs.
4. Present the review `summary` verbatim under a short heading, then `duration_s`. If `summary` was truncated, read `out_file` and show the rest.
5. Do not apply fixes. If the user wants them applied, they can ask; then treat each finding as a normal engineering task and verify it against the code before changing anything.
View on GitHub