Codex Review Workflow
CheckedAutomates code review tasks, flagging potential issues and suggesting improvements based on established coding standards.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add daffy0208/ai-dev-standards --skill codex-review-workflow -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
daffy0208
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned daffy0208/ai-dev-standards at 32c3241e48.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 32c3241e48
- Scanned
- 2 files, 406 lines
About this skill
What it does
The Codex Review Workflow automates code review tasks using the OpenAI Codex CLI. It facilitates iterative fix-and-review cycles to ensure code quality by automatically validating against established coding standards and identifying potential issues like bugs, security vulnerabilities, and adherence to best practices. The workflow guides users through a structured process of writing code, reviewing it with Codex, fixing any identified problems, and re-reviewing until satisfactory.
When to use it
- When a user explicitly requests a Codex CLI review (e.g., "Review this with Codex").
- For implementing features that require automated code validation.
- When building code that must meet specific quality standards.
- During iterative review and refinement cycles.
- To automatically validate for security, bugs, and best practices.
Key capabilities
- Automated code review using OpenAI Codex CLI.
- Structured 6-step workflow: Coding, Initial Review, Analysis, Fixes, Final Review, Reporting.
- Support for reviewing individual files or multiple files at once.
- Ability to specify a working directory context for reviews.
- Option to use specific OpenAI models (e.g.,
gpt-5-codex). - Customizable configuration options via Codex CLI flags.
Example prompts
Here are some example prompts you can give an AI agent with this skill:
- "Review the code in
auth.pyfor bugs, security issues, and best practices." - "Review the files
user.pyandsession.pyfor potential improvements. Provide specific feedback with line numbers." - "Review the code in
/path/to/project/email_validator.pyfor vulnerabilities."
Tips & gotchas
- Prerequisites: The Codex CLI must be installed and available on your system's PATH. A Git repository is also required (unless you use the
--skip-git-repo-checkflag, which isn’t recommended for production). - Specificity is key: Be specific in your prompts about what aspects of the code to review. Requesting line numbers and examples helps ensure actionable feedback.
- Timeout: Consider setting an appropriate timeout (120000ms or 2 minutes is recommended) for Codex CLI reviews.