codex-review
This tool automates code reviews and generates project changelogs based on commit history and modifications.
Install
mkdir -p .claude/skills/codex-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1514" && unzip -o skill.zip -d .claude/skills/codex-review && rm skill.zipInstalls to .claude/skills/codex-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Professional code review with auto CHANGELOG generation, integrated with Codex AIKey capabilities
- →Perform automated code reviews
- →Generate project CHANGELOG files
- →Review refactoring changes
How it works
The tool integrates with Codex AI to analyze code changes and automatically update the project documentation.
Inputs & outputs
When to use codex-review
- →Perform automated code reviews before commit
- →Generate project CHANGELOG files
- →Review large-scale refactoring changes
About this skill
codex-review
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
- Install the skill using the command above
- Ensure Codex CLI is installed
- Use
/codex-reviewor natural language triggers
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
When not to use it
- →Projects not using conventional commit messages
- →Environments without Codex CLI access
Prerequisites
Limitations
- →Requires adherence to conventional commit standards for best results
How it compares
It automates the generation of changelogs and review feedback compared to manual documentation and peer review processes.
Compared to similar skills
codex-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| codex-review (this skill) | 5 | 6mo | Review | Beginner |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| shellcheck-configuration | 9 | 2mo | No flags | Intermediate |
| wolf-scripts-core | 5 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by davila7
View all by davila7 →You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
shellcheck-configuration
wshobson
Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.
wolf-scripts-core
Nice-Wolf-Studio
Core automation scripts for archetype selection, evidence validation, quality scoring, and safe bash execution
python-code-style
wshobson
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
code-review-excellence
wshobson
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
code-walk-thru
pchalasani
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.