review

Reviewer-only pass for /plan --review and cleanup artifact review

18,211 stars

Best use case

review is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Reviewer-only pass for /plan --review and cleanup artifact review

Teams using review should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/review/SKILL.md --create-dirs "https://raw.githubusercontent.com/Yeachan-Heo/oh-my-codex/main/skills/review/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/review/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How review Compares

Feature / AgentreviewStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Reviewer-only pass for /plan --review and cleanup artifact review

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Review (Reviewer-Only Pass)

Review is a shorthand alias for `/plan --review`. It triggers Critic evaluation of an existing plan and is intended to preserve writer/reviewer separation.

## Usage

```
/review
/review "path/to/plan.md"
```

## Behavior

This skill invokes the Plan skill in review mode:

```
/plan --review <arguments>
```

The review workflow:
1. Treat review as a reviewer-only pass. The authoring context may write the plan or cleanup proposal, but a separate reviewer context must issue the verdict.
2. Read plan file from `.omx/plans/` (or specified path)
3. Evaluate via Critic agent
4. For cleanup/refactor/anti-slop work, confirm the artifact includes a cleanup plan, regression-test coverage or an explicit test gap, bounded smell-by-smell passes, and quality gates.
5. Return verdict: APPROVED, REVISE (with specific feedback), or REJECT (replanning required)

## Guardrails

- Never write and approve in the same context.
- If the current context authored the artifact, hand review to Critic or another reviewer role.
- Approval must cite concrete evidence, not author claims.

Follow the Plan skill's full documentation for review mode details.