codex-code-review

Reviews code changes via Codex exec and produces severity-grouped findings with a merge gate.

189|25|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/sd0xdev/sd0x-harness --skill codex-code-review-sd0xdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-code-review
Source: https://github.com/sd0xdev/sd0x-harness/tree/main/skills/codex-code-review
Command: npx skills add https://github.com/sd0xdev/sd0x-harness --skill codex-code-review-sd0xdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? It automates independent code review of diffs, uncommitted work, and full branches, producing severity-classified findings and a deterministic Ready/Blocked merge gate instead of ad-hoc manual review. ## Core Features & Use Cases - Three review variants: Fast (diff only), Full (diff plus lint/build pre-checks), and Branch (whole feature branch against a resolved merge base). - Frozen scope baseline: Computes the changed-file set once per session so every dispatch and re-review judges the same change. - Fallback and dual review: On Codex failure a contract-aware fallback reviewer carries the gate fail-closed; an optional --dual mode adds a second reviewer with conservative field-level merging. - Use Case: Before merging a feature branch, run the branch review to get P0/P1/P2/Nit findings with scope classification, acceptance-criteria coverage, and a gate verdict deciding whether the branch can proceed to precommit. ## Quick Start Ask the assistant to run a Codex code review on the current changes, for example by requesting a full review of the working tree before committing.

Frequently Asked Questions about codex-code-review

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

FAQPage Schema
How do I run an automated code review on my git changes?▼

Invoke the review with a variant matching your scope: fast for the current diff, full for the diff plus lint and build pre-checks, or branch for an entire feature branch. The reviewer reads the diffs itself and returns severity-grouped findings with a merge gate.

What is the difference between the fast, full, and branch review variants?▼

Fast reviews only the diff against HEAD with no pre-checks. Full adds lint:fix and build pre-checks before the same diff review. Branch resolves a merge base once and reviews all committed plus uncommitted work on the branch at the thorough tier.

What happens when Codex CLI fails during a review?▼

On adapter exit 1 (codex_fail), a contract-aware fallback reviewer is dispatched via the Task tool and its report is validated fail-closed before carrying the gate. If all fallback carriers are exhausted, no verdict is emitted and the gate surfaces as needing a human.

When should I not use this code review skill?▼

Use doc-review for document review, security-review for security-specific audits, test-review for coverage analysis, and code-explore when you only want to understand code rather than gate a change.

How does the review decide between Ready and Blocked?▼

The gate is derived from findings, not declared: an in-scope finding at or above the tier's blocking severity, an admitted finding at any severity, or an out-of-scope P0/security/data-integrity finding yields Blocked; otherwise Ready with gate_reason NONE.