codex-review

Review code changes via the locally installed OpenAI Codex CLI.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/croban/ai-dev-blueprint --skill codex-review-croban
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-review
Source: https://github.com/croban/ai-dev-blueprint/tree/main/skills/codex-review
Command: npx skills add https://github.com/croban/ai-dev-blueprint --skill codex-review-croban

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the hassle of manually running the OpenAI Codex CLI to get a second AI perspective on your code, saving you time on code reviews, architectural audits, and spec-source alignment checks.

Core Features & Use Cases

  • Structured Diff Review: Run Codex's built-in review mode on uncommitted changes, specific branches, or commits to catch bugs, security flaws, and style issues with file:line citations.
  • Free-Form Code Audits: Ask Codex to perform spec-vs-source parity checks, cross-repo code comparisons, or answer targeted architectural questions across any files on your local filesystem.
  • Use Case: After finishing a new feature, use this Skill to get a thorough review of all uncommitted changes without having to manually construct and run Codex CLI commands.

Quick Start

Invoke the codex-review skill to run a structured review of your uncommitted code changes and get actionable, cited feedback.

Frequently Asked Questions about codex-review

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

FAQPage Schema
How do I get a second AI opinion on uncommitted code changes?

A second AI opinion on uncommitted code changes is generated by running Codex CLI's structured review mode, which catches bugs and security flaws while providing actionable file:line citations.

Can I perform a cross-repository code audit on local filesystems without manual CLI operation?

Cross-repository code audits on local filesystems are supported through free-form queries that validate file access before analysis, enabling cross-repo comparisons and architectural question answering.

Does the Codex CLI code review process enforce read-only sandbox defaults?

The Codex CLI code review process enforces read-only sandbox defaults, validating file access before analysis to ensure safe, structured, and cited findings without modifying source files.

What is the best way to check spec-source alignment across multiple repositories?

Checking spec-source alignment is best handled through free-form code audits that perform spec-vs-source parity checks across local filesystems, surfacing structured and cited findings for divergence.

How do I validate architectural design decisions against existing source code?

Validating architectural design decisions involves asking targeted coding questions across local filesystems, using Codex CLI to surface structured, cited findings regarding spec-source alignment.