codex-review

Run a one-shot Codex review of files, diffs, artifacts, or descriptions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/KMakayee/playbook --skill codex-review-kmakayee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-review
Source: https://github.com/KMakayee/playbook/tree/main/.claude/skills/codex-review
Command: npx skills add https://github.com/KMakayee/playbook --skill codex-review-kmakayee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you catch correctness issues, oversights, and simpler alternatives by running a focused Codex second-opinion pass over a file, diff, artifact, or freeform description.

Core Features & Use Cases

  • One-shot review over flexible inputs: Review a file path, a diff, a generated artifact (like a plan or design doc), or a written description.
  • Three-lens finding structure: Produces findings under Factual / correctness, Simplest-approach, and Pattern / best-practice, with each finding classified as factual issue or judgment call.
  • Actionability checks: Encourages specific locations (line numbers or headings) so findings are easier to verify and act on.

Quick Start

Use the codex-review skill to review the file tasks/design-decision.md.

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 opinion on a code diff before merging?

A code review second opinion surfaces correctness problems, simpler approaches, and best-practice gaps. It groups findings into factual issues and judgment calls across correctness, simplest-approach, and best-practice lenses.

Can I review a design document or freeform technical description?

You can review design documents or freeform technical descriptions. The evaluation checks for correctness issues, simpler alternatives, and best-practice gaps, returning actionable findings with specific locations.

What does a Codex review check for in a generated artifact?

A Codex review checks generated artifacts for correctness problems, simpler approaches, and pattern gaps. Each finding is classified as a factual issue or a judgment call to clarify its severity.

Does the review output include specific line numbers or headings?

Yes, the review output includes specific line numbers or headings to make findings easier to verify and act on. This actionability check ensures you can locate and address each correctness issue or best-practice gap.

What's the best way to classify code review findings objectively?

Classify code review findings objectively by separating factual issues from judgment calls. The review applies three lenses—factual correctness, simplest-approach, and pattern best-practice—to distinguish verifiable errors from subjective preferences.

Do I need any dependencies or components to run a Codex review?

No dependencies or components are required to run a Codex review. The skill operates independently to perform read-only execution output capture, spot-check cited claims, and structure findings grouped by evaluation lenses.