// Requests an independent code review from OpenAI Codex CLI, critically evaluates its findings, and applies warranted fixes. Activates when: the user says /codex-review, asks for a Codex review, or wants an external AI review of changes.
| name | codex-review |
| description | Requests an independent code review from OpenAI Codex CLI, critically evaluates its findings, and applies warranted fixes. Activates when: the user says /codex-review, asks for a Codex review, or wants an external AI review of changes. |
| user_invocable | true |
Run an independent code review using OpenAI Codex CLI, then critically evaluate and apply warranted findings.
Check what has changed:
git diff --stat HEAD
git diff --stat --staged
If there are uncommitted changes, review those (--uncommitted). If the working tree is clean, review the latest commit (--commit HEAD).
Run the appropriate command:
For uncommitted changes:
codex exec review --full-auto --uncommitted "Review for correctness, security, edge cases, and test coverage gaps. Adapt focus areas to the project at hand by reading composer.json and README.md before forming the prompt. Be concise — only report real issues, not style preferences."
For the latest commit:
codex exec review --full-auto --commit HEAD "Review for correctness, security, edge cases, and test coverage gaps. Adapt focus areas to the project at hand by reading composer.json and README.md before forming the prompt. Be concise — only report real issues, not style preferences."
For changes against main:
codex exec review --full-auto --base main "Review for correctness, security, edge cases, and test coverage gaps. Adapt focus areas to the project at hand by reading composer.json and README.md before forming the prompt. Be concise — only report real issues, not style preferences."
Codex findings are suggestions, not mandates. For each finding:
For findings that are genuine issues:
vendor/bin/pest --no-coverage to verifyvendor/bin/phpstan analyse src/ --memory-limit=2G to verifySummarize to the user:
## Codex Review Summary
### Applied
- [Issue] — [What was wrong and how you fixed it]
### Dismissed
- [Finding] — [Why it was dismissed: false positive / already tested / style preference]
### No Issues
- [Categories that were clean]
MUST USE when creating, updating, or managing AI skills and guidelines. Activates when: creating a new skill, editing existing skills, updating coding guidelines, modifying AI instructions, working with .ai/ directory, or when user mentions: skill, CLAUDE.md, guidelines, AI configuration.
Author a boost.php config file. Covers all five with* methods, when each matters, and what NOT to put in there.
Test-driven bug fixing workflow. Activates when: fixing bugs, debugging issues, resolving defects, investigating errors, or when user mentions: bug, fix, broken, not working, error, issue, defect, regression.
Applies PR review feedback with critical evaluation. Activates when: applying review comments, addressing PR feedback, responding to code review, or when user mentions: review feedback, PR comments, apply feedback, address comments, reviewer feedback.
Pre-push / pre-release checklist. Runs Rector, Pint, full test suite, PHPStan, and audits README + `.ai/` docs for staleness. Activate before: pushing to remote, tagging a release, writing release notes, or when user mentions: pre-release, pre-push, release checklist, ship, cut release, release notes.
Implement a FileEmitter for boost-core to emit a custom file (e.g. .mcp.json, .editorconfig) into the host project during boost:sync.