review

Evaluate plan files in .omx/plans/ with Critic-based review verdicts.

32.6k|2.5k|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/Yeachan-Heo/oh-my-codex --skill review-yeachan-heo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Yeachan-Heo/oh-my-codex/tree/main/skills/review
Command: npx skills add https://github.com/Yeachan-Heo/oh-my-codex --skill review-yeachan-heo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Alias for the plan review workflow streamlines validation by delegating to the Plan skill's review mode.

Core Features & Use Cases

  • Alias for /plan --review, enabling quick critique of existing plans
  • Triggers Critic evaluation and returns structured verdicts (APPROVED, REVISE, REJECT) with actionable feedback
  • Works with plans stored in .omx/plans/ or a specified path, preserving plan integrity

Quick Start

Initiate a review by running /review on the target plan.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review an existing plan file using Critic evaluation?

You can review an existing plan file by running the review command on your target plan path. This triggers Critic evaluation and returns structured verdicts such as APPROVED, REVISE, or REJECT with actionable feedback.

What is the difference between APPROVED, REVISE, and REJECT verdicts in plan evaluation?

Plan evaluation verdicts determine the next step for your workflow: APPROVED means the plan passes validation, REVISE indicates changes are needed, and REJECT means the plan requires complete rework. Each verdict includes actionable feedback to guide your updates.

Can I specify a custom file path for plan review instead of the default directory?

Yes, you can specify a custom file path for plan review instead of using the default .omx/plans/ directory. The review process preserves plan integrity regardless of the specified location and applies the same Critic-based evaluation logic.

Does the plan review workflow require any dependencies or components to function?

The plan review workflow operates as an alias to rapidly review plans with Critic and requires no additional dependencies or components. It directly evaluates plan files and returns structured verdicts without needing external modules.

Why does my plan review workflow return a REVISE verdict instead of APPROVED?

A plan review workflow returns a REVISE verdict instead of APPROVED when the Critic evaluation identifies issues requiring changes before the plan can pass validation. The accompanying actionable feedback details the specific revisions needed to achieve approval.