review

Route plan reviews through Critic and return APPROVED, REVISE, or REJECT verdicts.

6|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Goblin1024/oh-my-kimi --skill review-goblin1024
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Goblin1024/oh-my-kimi/tree/main/skills/review
Command: npx skills add https://github.com/Goblin1024/oh-my-kimi --skill review-goblin1024

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewer-only pass for plan evaluation ensures separation of roles and prevents self-approval by authors, routing critiques through a formal Critic workflow.

Core Features & Use Cases

  • Role-separation enforcement: mandates separate author and reviewer contexts and documents verdicts.
  • Plan-verification workflow: reads plans from .omk/plans/ (or a specified path) and validates required review artifacts (e.g., critique notes, evidence, and suggested actions).
  • Verdict-based outcomes: returns structured results such as APPROVED, REVISE, or REJECT with concrete feedback.

Quick Start

Submit the plan file to be reviewed and trigger Critic evaluation.

Frequently Asked Questions about review

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

FAQPage Schema
How do I enforce role separation to prevent self-approval of a plan?

To enforce role separation during plan evaluation, this review workflow mandates separate author and reviewer contexts, routing critiques through a formal process to prevent authors from self-approving their own plans.

What is a standardized workflow for returning a plan review verdict?

A standardized plan review verdict is a structured outcome such as APPROVED, REVISE, or REJECT, generated after validating critique notes, evidence, and suggested actions within the plan file.

How do I validate regression-test coverage and test gaps in a plan review?

You validate regression-test coverage and explicit test gaps by routing the existing plan through a Critic evaluation, which checks for bounded smells, quality gates, and cleanup plans before returning a verdict.

Can I review plans located outside the default .omk/plans/ directory?

Yes, you can review plans located outside the default .omk/plans/ directory by providing a specified file path to the evaluation workflow when submitting the plan for critique.

Does the plan review workflow require specific cleanup plans and quality gates?

Yes, the plan review workflow requires specific cleanup plans and quality gates, validating these required review artifacts alongside regression-test coverage to ensure evidence-based verdicts.

When should I not use an automated critic workflow for plan evaluation?

You should not use an automated critic workflow for plan evaluation if your project lacks established author and reviewer contexts, as the system strictly enforces this role separation to generate valid verdicts.