codex-review-workflow

Automates iterative code review cycles using OpenAI Codex CLI until validation passes.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/Yash-Awasthi/adapfit --skill codex-review-workflow-yash-awasthi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-review-workflow
Source: https://github.com/Yash-Awasthi/adapfit/tree/main/.agents/skills/codex-review-workflow
Command: npx skills add https://github.com/Yash-Awasthi/adapfit --skill codex-review-workflow-yash-awasthi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing code for bugs, security vulnerabilities, and best practices is time-consuming and inconsistent. This Skill automates the review process by running OpenAI Codex CLI in structured fix-and-review cycles, ensuring code meets quality standards before completion. ## Core Features & Use Cases - Automated Review Execution: Runs codex exec commands against files or file groups to detect bugs, security issues, and maintainability problems with line-specific feedback. - Iterative Fix-and-Review Cycles: Applies fixes for identified issues, then re-reviews with targeted prompts to confirm resolution, up to a 2-iteration limit. - Structured Result Analysis: Parses Codex output sections (Bug, Security, Key Issues, Resolved Checks) to determine pass/fail status and decide whether to continue iterating. - Use Case: After implementing a user authentication module, run this Skill to automatically detect issues like missing password hashing or SQL injection, fix them, and verify the fixes through a follow-up review. ## Quick Start Ask the AI to implement your feature and review it with Codex, for example: "Implement user authentication and run it through Codex review."

Frequently Asked Questions about codex-review-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an automated code review with Codex CLI?▼

Use `codex exec` with a specific review prompt, such as asking it to review a file for bugs, security issues, and best practices with line numbers. Note that `codex exec` is required, not `codex review`, and reviews typically take 30-120 seconds.

How many review iterations should an automated code review run?▼

This workflow limits reviews to 2 cycles: one initial review plus one follow-up review after fixes. The limit prevents infinite loops, since some issues require human judgment or architectural changes beyond automated fixing.

Does Codex CLI require a git repository to run reviews?▼

Yes, Codex CLI requires a git repository by default. Run `git init` if your project is not yet a repository, or pass the `--skip-git-repo-check` flag, though skipping is not recommended for production work.

Why does Codex CLI fail with an unexpected argument error?▼

This error usually occurs when using `codex review` instead of the correct `codex exec` command. Check your syntax, verify installation with `codex --version`, and ensure you are authenticated via `codex login` if needed.

When should I skip automated Codex code review?▼

Skip it when Codex CLI is unavailable in the environment, when the task is purely exploratory or research-based, or when the code is simple enough that formal review adds no value. Manual review remains appropriate for nuanced architectural decisions.