patch-approval

Reviews Codex-generated patch diffs in an isolated git clone before applying them to the workspace.

6|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Jerrylalala/compound-engineering --skill patch-approval-jerrylalala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: patch-approval
Source: https://github.com/Jerrylalala/compound-engineering/tree/main/plugins/compound-engineering/skills-custom/patch-approval
Command: npx skills add https://github.com/Jerrylalala/compound-engineering --skill patch-approval-jerrylalala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When Codex returns code changes as a patch or diff, applying them blindly risks introducing security flaws, unintended side effects, or out-of-scope edits. This Skill inserts a Claude approval layer between Codex output and your working tree so every patch is inspected before it touches your files. ## Core Features & Use Cases - Isolated Execution: Runs Codex inside a temporary git clone copy and captures changes with git diff, since Codex CLI has no --dry-run flag. - Structured Approval Checklist: Evaluates patches across Blocking (security), Analytical (correctness), and Advisory (scope) dimensions, with pass / modified-pass / reject decisions. - User Confirmation & Audit Trail: Shows a patch summary for gated changes and records the verdict in state.md for traceability. - Use Case: You route a refactoring task to Codex via the Codex-first Executor. Codex produces a diff touching three files; Claude reviews it, fixes a minor naming issue, presents the summary, and applies the patch only after your confirmation. ## Quick Start Ask Claude to run the Codex task in an isolated directory and approve the resulting patch before applying it to my repository.

Frequently Asked Questions about patch-approval

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

FAQPage Schema
How do I review Codex CLI patches before applying them?▼

Run Codex inside a temporary git clone of your repository, capture the changes with git diff, then have Claude evaluate the patch against a security, correctness, and scope checklist. The patch is applied only after approval and optional user confirmation.

Does Codex CLI support a dry-run mode for safe patch generation?▼

No, Codex CLI does not support a --dry-run flag as of v0.118 and later. The safe alternative is executing Codex in an isolated directory created with git clone --local, then extracting the changes with git diff.

What checks should a code patch approval process include?▼

A patch approval checklist should cover blocking security issues like injection and hardcoded secrets, analytical correctness such as matching task intent and avoiding side effects, and advisory scope concerns like unexpected extra changes or deletions.

What happens when a Codex patch fails the approval review?▼

When blocking checks fail, the patch is rejected and the workflow falls back to Claude executing the task directly. Minor analytical issues allow Claude to modify the patch and apply the corrected version instead.

What are the limitations of isolated-directory patch approval?▼

The approach requires the workspace to be a git repository with local clone support, does not apply patches automatically without user confirmation, and falls back to Claude execution when Codex patches produce complex conflicts.