Claude Codex Review Skill banner
Serg2000Mr Serg2000Mr

Claude Codex Review Skill

Code Quality community

Description

File-based dual-review skill for Claude Code + Codex: iterative plan/code review through plain files, no MCP server needed

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

[Русская версия](README.ru.md)

Claude-Codex Review Skill

This skill lets Claude Code and Codex review a plan or code change through a crash-resilient file protocol. Claude Code initiates the session, Codex acts as an independent reviewer, and both agents use the same project directory without an MCP server or CLI bridge.

Quick start

Copy the complete `claude-code/` directory into the project skill directory:

mkdir -p .claude/skills/codex-dual-review-file-based
cp claude-code/* .claude/skills/codex-dual-review-file-based/

Then run in Claude Code:

/codex-dual-review-file-based  [path/to/plan.md] [max_rounds=5]

Claude Code creates the first round and prints one ready-to-use instruction for Codex. Codex keeps watching the same session for later rounds; the user does not need to pass the prompt again.

How it works

Each session lives in an absolute `/.dual-review//` directory. If Claude Code runs inside a Git worktree, the session remains inside that worktree.

R1-01-round-start.md     <- Claude writes the review contract
R1-02-codex-claimed.flg  <- Codex claims the round
R1-03-codex-review.md    <- Codex writes the review
R1-04-claude-claimed.flg <- Claude processes the result
final.md                 <- Claude records the session outcome

Round-start and review files contain a machine-readable JSON block plus a human-readable explanation. Claude verifies every finding as a hypothesis, applies accepted changes before opening the next round, and records rejected findings with evidence.

The session ends with:

  • approved after APPROVED;
  • failed after the rare REJECTED verdict;
  • limit when max_rounds is reached.

`APPROVED` alone does not finish a session: `final.md` is the completion marker.

Protocol guarantees

  • Session files are append-only: protocol files are never overwritten or deleted.
  • Absolute SESSION_DIR, reviewer-prompt, and helper-script paths