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".
Quellinformationen
- Repository
- collisionengineers/claude-using-codex-skill
- Letzte Quellaktivität
- 3. September 2026 um 15:39
- Erkannte Sprache von SKILL.md
- Englisch
- Sterne
- 0
- Forks
- 0
Installationsoptionen
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
SKILL.md wird angezeigt
SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau- 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.
Auf GitHub ansehen