review

Review plans under .omb/plans with Critic evaluation and guardrail checks.

3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Tienching/oh-my-codebuddy --skill review-tienching
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Tienching/oh-my-codebuddy/tree/main/skills/review
Command: npx skills add https://github.com/Tienching/oh-my-codebuddy --skill review-tienching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Reviewer-only evaluation of plans, ensuring independent verdicts.
  • Enforces writer/reviewer separation and documents concrete feedback.
  • Validates artifacts for required guardrails such as cleanup plans and regression tests.

Quick Start

Invoke the reviewer context and run /plan --review to begin the evaluation.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review and evaluate a project plan for quality gates?

Plan review evaluates existing plan artifacts to enforce quality gates, checking for required cleanup plans and regression tests before providing an evidence-based approval verdict.

What is writer and reviewer separation in plan evaluation?

Writer and reviewer separation ensures an independent reviewer evaluates plan artifacts, preventing the original author from approving their own work and enforcing objective, evidence-based feedback.

How do I validate that a plan includes a cleanup plan and regression tests?

Validating a plan involves invoking a reviewer context to assess stored artifacts, specifically enforcing guardrails that require an explicit cleanup plan and regression tests before approval.

Can I evaluate existing plans stored in a local directory?

Yes, you can evaluate existing plans stored under the .omb/plans directory by invoking a reviewer-only evaluation pass that assesses the artifacts and documents concrete feedback.

What happens if my plan artifacts lack explicit evidence for feedback?

If plan artifacts lack explicit evidence, the review process withholds approval, as the evaluation mechanism enforces evidence-based feedback and requires artifacts to pass all guardrails.