codex-review
Run automated code review using Codex CLI. Use when the user wants an automated code review of uncommitted changes, a specific commit, or changes against a base branch. This skill runs `codex review` non-interactively and returns structured feedback — it does not post comments on PRs or interact with GitHub.
Best use case
codex-review is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run automated code review using Codex CLI. Use when the user wants an automated code review of uncommitted changes, a specific commit, or changes against a base branch. This skill runs `codex review` non-interactively and returns structured feedback — it does not post comments on PRs or interact with GitHub.
Teams using codex-review should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/codex-review/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How codex-review Compares
| Feature / Agent | codex-review | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run automated code review using Codex CLI. Use when the user wants an automated code review of uncommitted changes, a specific commit, or changes against a base branch. This skill runs `codex review` non-interactively and returns structured feedback — it does not post comments on PRs or interact with GitHub.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
SKILL.md Source
<!-- Example prompts: /codex-review Review my uncommitted changes /codex-review Review changes against the correct base branch /codex-review Review the last commit --> You are a code review coordinator. When invoked, run a code review using the bundled Codex CLI binary. ## How to Review Use `codex review` with the appropriate flags: ### Review uncommitted changes (staged, unstaged, and untracked) ```bash codex review --uncommitted ``` ### Review changes against a base branch ```bash codex review --base <resolved-base-branch> ``` ### Review a specific commit ```bash codex review --commit <SHA> ``` ### Review with custom instructions `[PROMPT]` is a positional argument that **cannot** be combined with `--uncommitted`, `--base`, or `--commit`. Use it alone for a free-form review prompt: ```bash codex review "Focus on error handling and edge cases" ``` ## Workflow 1. **Determine scope**: Ask the user what they want reviewed if not clear — uncommitted changes, a branch diff, or a specific commit. 2. **Resolve the base branch when needed**: For branch diff reviews, determine the correct base branch before running `codex review --base`. 3. **Run the review**: Execute `codex review` with the appropriate flags. 4. **Present findings**: Share the review output with the user. Highlight critical issues separately from suggestions. 5. **Discuss**: If the user wants to act on specific feedback, help them implement the changes. ## Resolving the Base Branch When reviewing a branch diff, do not assume the base branch is `main`. - If the user explicitly names a base branch, use it. - If the branch may be part of a stacked PR flow, use the `adjust-pr-base` skill's discovery procedure through step 3 only to identify the nearest open parent PR branch. - If you are already using the `stacked-pr` skill for the current task, reuse its branch relationship discovery instead of deriving the base separately. - If a nearest open parent PR branch exists, use it as the review base. - Otherwise use the repository default branch as the review base. After resolving the base branch, run: ```bash codex review --base <resolved-base-branch> ``` ## Important Guidelines - Default to `--uncommitted` when the user says "review my changes" without further detail - For branch diff reviews, resolve the correct base branch first instead of assuming `main` - In a stacked PR workflow, prefer the nearest open parent PR branch as the review base - The review runs non-interactively and returns structured feedback - Treat the review as advisory — not all suggestions need to be applied ## Help !`codex review --help`
Related Skills
triage-pr-reviews
Triages unresolved PR review comments using gh-pr-reviews. Analyzes code context and classifies each comment as Agree / Partially Agree / Disagree. Walks through each comment one-by-one, asking the user what action to take. Use when the user wants to triage, review, or analyze unresolved PR comments.
review-plan
Diagnostically review an implementation plan against the current codebase. Focuses on problem framing, expected behavior, and architecture decisions. This skill is read-only — it does not edit files or rewrite the plan.
github-pr-review-operation
GitHub Pull Request上でのレビュー操作を行うスキル。ghコマンドでPR情報取得、差分確認、コメント投稿・取得、インラインコメント、コメント返信を実行する。PRにコメントを投稿したい、差分を行番号付きで確認したい、レビューコメントに返信したいときに使用。
typescript-performance
Comprehensive TypeScript performance analysis and optimization. Use when users report slow TypeScript compilation, slow editor experience, or want to investigate TypeScript performance issues. This skill provides diagnostic tools, trace analysis workflows, and optimization strategies. Key triggers include mentions of slow builds, type-checking delays, tsc performance, editor lag with TypeScript, or requests to analyze/improve TypeScript performance. Always prioritize data-driven analysis using --extendedDiagnostics, --generateTrace, and TS Server logs before making optimization recommendations.
watch-ci
CI を監視し、失敗したら自律的に修正してパスするまでループするスキル。push 後・PR 作成後・rebase 後に CI が通るか確認したいとき、CI が落ちていたら直してほしいとき、CI の結果を待ちたいときに使う。「CI 監視して」「CI が通るまで待って」「CI 直して」「push したので CI を見ておいて」など、CI の状態確認・自動修正が必要な場面では必ずこのスキルを呼び出すこと。
vue-style-guide
Vue を書くときは基本的に参考にしてください。 個人的に気に入っている ubgeeei 氏の Vue.js のスタイルガイドです。
vitess
Vitess best practices, query optimization, and connection troubleshooting for PlanetScale Vitess databases. Load when working with Vitess databases, sharding, VSchema configuration, keyspace management, or MySQL scaling issues.
terraform-test
Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, or troubleshooting Terraform test syntax and execution.
terraform-style-guide
Generate Terraform HCL code following HashiCorp's official style conventions and best practices. Use when writing, reviewing, or generating Terraform configurations.
terraform-stacks
Comprehensive guide for working with HashiCorp Terraform Stacks. Use when creating, modifying, or validating Terraform Stack configurations (.tfcomponent.hcl, .tfdeploy.hcl files), working with stack components and deployments from local modules, public registry, or private registry sources, managing multi-region or multi-environment infrastructure, or troubleshooting Terraform Stacks syntax and structure.
teach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
stacked-pr
依存関係のある複数の PR を管理・同期するためのスキル。stacked PR のカスケード rebase、PR 間の依存検出、base branch 管理、CI の上流優先修正を行う。PR が別の PR に依存している状況全般で使う — cascade rebase、スタック sync、依存先 PR 更新後のメンテ、PR チェーンの整合性確認などをするときなど。