codex-impl-review

Automate adversarial code review of uncommitted changes or branch differences using the Codex CLI.

69|23|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/lploc94/codex_skill --skill codex-impl-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-impl-review
Source: https://github.com/lploc94/codex_skill/tree/main/skill-packs/codex-review/skills/codex-impl-review
Command: npx skills add https://github.com/lploc94/codex_skill --skill codex-impl-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the review of code changes, ensuring quality and catching potential issues before they are committed or merged.

Core Features & Use Cases

  • Pre-commit Review: Analyze uncommitted code changes for bugs, security vulnerabilities, and style issues.
  • Branch Review: Review differences between your current branch and a base branch before merging.
  • Iterative Feedback: Engages in a debate with Codex, allowing for fixes and rebuttals until consensus is reached.
  • Use Case: Before committing a new feature, run this skill to get an AI-powered review of your changes, identifying potential regressions or style guide violations.

Quick Start

Use the codex-impl-review skill to review my uncommitted code changes.

Frequently Asked Questions about codex-impl-review

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

FAQPage Schema
How do I automate code review for uncommitted changes before a git commit?

To automate code review for uncommitted changes before a git commit, this Skill uses the Codex CLI to perform an adversarial analysis of your working directory, identifying bugs and style issues. It facilitates an iterative debate with Codex to resolve any detected issues before you commit.

Can I review branch differences for regressions before merging code?

Yes, you can review branch differences for regressions before merging code. This Skill compares your current branch against a base branch to identify potential security vulnerabilities or style guide violations, ensuring correctness and adherence to best practices prior to a merge.

How does the iterative debate mechanism work during an AI code review?

The iterative debate mechanism works by engaging you and Codex in a feedback loop during the AI code review. You can apply fixes or provide rebuttals to the identified issues, continuing the debate until a consensus on code quality and correctness is reached.

Can I configure the review depth for my pre-commit code analysis?

Yes, you can configure the review depth for your pre-commit code analysis. This Skill supports configurable effort levels, allowing you to adjust the depth of the adversarial review performed by the Codex CLI based on your specific quality assurance requirements.

What is the best way to catch security vulnerabilities in uncommitted code changes?

The best way to catch security vulnerabilities in uncommitted code changes is to run an adversarial code review using this Skill. It analyzes your working changes via the Codex CLI, enabling an iterative debate to ensure all security and style issues are resolved before committing.