Overview
Professional code review with auto CHANGELOG generation, integrated with Codex AI
When to Use
- When you want professional code review before commits
- When you need automatic CHANGELOG generation
- When reviewing large-scale refactoring
Installation
npx skills add -g BenedictKing/codex-review
Step-by-Step Guide
- This entrypoint does not bundle the upstream integration. Inspect a selected upstream revision and authorize installation scope before using the installation option above.
- Ensure Codex CLI is installed
- Use
/codex-reviewonly when the installed host exposes it. Pin repository/base/head and inspect the net diff directly; return findings with exact trigger, location and evidence. A generated CHANGELOG must match the actual diff and must not rewrite unrelated release history.
Examples
See GitHub Repository for examples.
Best Practices
- Keep CHANGELOG.md in your project root
- Use conventional commit messages
Troubleshooting
See the GitHub repository for troubleshooting guides.
Related Skills
- context7-auto-research, tavily-web, exa-search, firecrawl-scraper
Limitations
- An automated reviewer is advisory, not merge approval. Confirm provider/data/cost scope before sending private source externally; no implicit commit, push or publication.
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.