codex-review
Codex Code Review
Overview
Use the OpenAI Codex CLI to perform AI-powered code reviews. Supports reviewing branches, uncommitted changes, specific commits, and custom-scoped reviews. Reviews are read-only and never modify the working tree.
Prerequisites
- Codex CLI installed (
npm i -g @openai/codex) - Authenticated (
codex login)
Workflow
Step 1: Determine Review Scope
Ask the user what they want reviewed if not already clear:
| Scope | When to use |
|---|---|
| Branch diff | Before opening or merging a PR |
| Uncommitted changes | During active development |
| Specific commit | Auditing a single changeset |
| Custom | User provides specific review instructions |
Step 2: Run the Review
Branch review (compare current branch against base):
codex review --base main -c model="gpt-5.3-codex"
Uncommitted changes:
codex review --uncommitted -c model="gpt-5.3-codex"
Specific commit:
codex review --commit <SHA> -c model="gpt-5.3-codex"
Custom review with focused instructions:
codex review -c model="gpt-5.3-codex" "Review the code for accessibility regressions and WCAG compliance."
Common Flags
| Flag | Description |
|---|---|
--base <BRANCH> |
Review changes against a base branch |
--uncommitted |
Review staged, unstaged, and untracked changes |
--commit <SHA> |
Review changes introduced by a specific commit |
--title <TITLE> |
Optional commit title for the review summary |
-c model="gpt-5.3-codex" |
Override the model (preferred: gpt-5.3-codex) |
Rules
- Default to reviewing the current branch diff against
mainunless the user specifies otherwise - Always pass
-c model="gpt-5.3-codex"to use the preferred model - Use
--base,--uncommitted, or--commitflags to set the review scope instead of describing it in the prompt - Present findings sorted by priority (highest first)
- Summarize the overall assessment before listing individual findings
- If Codex CLI is not installed, instruct the user to run
npm i -g @openai/codexandcodex login
More from trancong12102/agentskills
deps-dev
Look up the latest stable version of any open-source package across npm, PyPI, Go, Cargo, Maven, and NuGet. Use when the user asks 'what's the latest version of X', 'what version should I use', 'is X deprecated', 'how outdated is my package.json/requirements.txt/Cargo.toml', or needs version numbers for adding or updating dependencies. Also covers pinning versions, checking if packages are maintained, or comparing installed vs latest versions. Do NOT use for private/internal packages or for looking up documentation (use context7).
151council-review
Multi-perspective code review that synthesizes findings from multiple reviewers into a unified report. Use when the user asks to review code changes, audit a diff, check code quality, review a PR, review commits, or review uncommitted changes. Also covers 'code review', 'review my changes', 'check this before I merge', or wanting multiple perspectives on code. Do not use for documentation/markdown review or trivial single-line changes.
95oracle
Deep analysis and expert reasoning. Use when the user asks for 'oracle', 'second opinion', architecture analysis, elusive bug debugging, impact assessment, security reasoning, refactoring strategy, or trade-off evaluation — problems that benefit from deep, independent reasoning. Do not use for simple factual questions, code generation, code review (use council-review), or tasks needing file modifications.
93context7
Fetch up-to-date documentation for any open-source library or framework. Use when the user asks to look up docs, check an API, find code examples, or verify how a feature works — especially with a specific library name, version migration, or phrases like 'what's the current way to...' or 'the API might have changed'. Also covers setup and configuration docs. Do NOT use for general programming concepts, internal project code, or version lookups (use deps-dev).
86conventional-commit
Generates git commit messages following Conventional Commits 1.0.0 specification with semantic types (feat, fix, etc.), optional scope, and breaking change annotations. Use when committing code changes or creating commit messages.
58react-web-advanced
Web-specific React patterns for type-safe file-based routing, route-level data loading, server-side rendering, search param validation, code splitting, and list virtualization. Use when building React web apps with route loaders, SSR streaming, validated search params, lazy route splitting, or virtualizing large DOM lists. Do not use for React Native apps — use react-native-advanced instead.
45