codex-review

Automates Codex-based plan and code reviews with iterative auto-fix loops.

9|1|Updated Jan 15, 2016
One-click install
npx skills add https://github.com/wadackel/dotfiles --skill codex-review-wadackel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-review
Source: https://github.com/wadackel/dotfiles/tree/main/home/programs/claude/skills/codex-review
Command: npx skills add https://github.com/wadackel/dotfiles --skill codex-review-wadackel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates structured Codex-based plan and code reviews, enabling teams to validate plans and code with iterative feedback until approval.

Core Features & Use Cases

  • Plan review using Codex MCP to evaluate implementation plans against project guidelines (CLAUDE.md)
  • Code review with workspace-write sessions and automatic follow-ups using codex-reply
  • Iterative fix loop that applies changes via Edit until issues are resolved
  • Use cases include plan validation, code quality audits, and security reviews

Quick Start

Read plan.md and CLAUDE.md, start a plan review with Codex MCP in read-only mode, then perform a code review with a workspace-write session and iterate via codex reply until all issues are resolved.

Frequently Asked Questions about codex-review

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

FAQPage Schema
How do I automate code review and iterative auto-fixes for my project?▼

Automated code review with iterative auto-fixes is achieved by using Codex MCP in a workspace-write session to collect diffs, evaluate them against project guidelines, and apply changes via Edit and codex-reply until issues are resolved.

How does Codex validate an implementation plan against coding standards?▼

Codex validates an implementation plan by running a read-only review session that evaluates your plan.md against the governance rules and coding standards defined in your project's CLAUDE.md context.

Can I use this iterative code review workflow for security and quality audits?▼

Yes, you can use this iterative code review workflow for security and quality audits by starting a Codex MCP session to check code diffs and automatically looping fixes until all security and quality issues pass.

Do I need Codex MCP to run iterative code diff reviews?▼

Yes, Codex MCP is required to run iterative code diff reviews because it drives the evaluation logic, while the Edit and codex-reply tools handle the automated fix loop for resolving detected issues.

What is the best way to handle follow-up iterations after a code review?▼

The best way to handle follow-up iterations after a code review is using the codex-reply tool to trigger automated loops that apply Edit changes until the workspace-write session reports all issues as resolved.

Why does my automated plan review require a CLAUDE.md file?▼

Automated plan review requires a CLAUDE.md file because it contains the project guidelines and coding standards that Codex MCP reads to vet the implementation plan during the read-only evaluation session.