Main Router
VCnoC/Claude-Code-Zen-mcp-Skill-Work
Intelligent skill router that analyzes user requests and automatically dispatches to the most appropriate skill(s) or zen-mcp tools.
Reviews finished work for correctness, risk, reuse and simplification, and reports verified findings most severe first without authoring the change.
Install OMC Review Workflow
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill omc-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Yeachan-Heo/oh-my-claudecode omc-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/review .claude/skills/omc-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "omc-review" agent skill from https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/review into .claude/skills/omc-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omc-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill omc-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Yeachan-Heo/oh-my-claudecode omc-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/review .agents/skills/omc-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "omc-review" agent skill from https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/review into .agents/skills/omc-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omc-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill omc-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Yeachan-Heo/oh-my-claudecode omc-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/review .cursor/skills/omc-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "omc-review" agent skill from https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/review into .cursor/skills/omc-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omc-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Yeachan-Heo/oh-my-claudecode.git --path skills/review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill omc-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Yeachan-Heo/oh-my-claudecode omc-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/review .gemini/skills/omc-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "omc-review" agent skill from https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/review into .gemini/skills/omc-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omc-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Yeachan-Heo/oh-my-claudecode omc-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill omc-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/review .github/skills/omc-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "omc-review" agent skill from https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/review into .github/skills/omc-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omc-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill omc-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Yeachan-Heo/oh-my-claudecode omc-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/review .opencode/skills/omc-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "omc-review" agent skill from https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/review into .opencode/skills/omc-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omc-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
omc-review- GitHub stars
- 40k
- Token cost
- ~655 tokens
- SKILL.md length
- 361 words
- Files
- 1
- Skills in repo
- 47
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reviews finished work for correctness, risk, reuse and simplification, and reports verified findings most severe first without authoring the change.
- Works in 5 steps: Establish what changed and what it was… → Read the change against that intent. → Check correctness first, then risk, then… → …
- Reviewing a finished change before it ships
- SKILL.md covers Goal, Workflow, What to check and Two axes, run apart, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Review evaluates work that already exists and never writes the change it is judging. The agent establishes what changed and what it was meant to do, reads the change against that intent, checks correctness first, then risk, then simplification, and verifies each candidate finding before reporting it. Checks cover logic defects, edge cases, error paths and concurrency, security boundaries, destructive operations, data integrity, missed reuse, code that could be deleted and behavior that ships untested.
A substantial diff is reviewed as two parallel sub-agent passes that are reported separately: one against the repo's documented standards, such as CLAUDE.md, AGENTS.md and docs/standards, and one against the task, spec or ticket acceptance criteria. A small diff gets one pass. The reviewer should not share the author's active context, severity is stated honestly, and no findings is a valid result. Output lists each finding with file, line and a concrete failure scenario, plus what was checked and found clean. Review is advisory by default, and release, security and destructive-operation gates stay separate.
When your agent uses it
- Reviewing a finished change before it ships
- Checking a diff against both repo standards and the original ticket
- Looking for risky or unnecessary code in work another agent wrote
Example prompts
- “Review the branch for the invoice export feature and rank anything that could break.”
- “Check this diff against the acceptance criteria in the ticket.”
- “Look over the changes from the last session for dead code and missed reuse.”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Establish what changed and what it was meant to do.
- Read the change against that intent.
- Check correctness first, then risk, then simplification.
- Verify each candidate finding before reporting it.
- Report findings most-severe first.
What it can do on your machine
Read from SKILL.md and the folder at commit 454bae0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
OMC Review Workflow loads about 655 tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 361 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Yeachan-Heo/oh-my-claudecode at commit 454bae0, republished under its MIT licence (© Yeachan-Heo). 361 words, ~655 tokens.
Download SKILL.mdSave it as
.claude/skills/omc-review/SKILL.md (or your agent's skills folder).- name
- omc-review
- description
- Evaluate finished work for defects, risk, and simplification before it ships
Review
Use this skill to evaluate work that already exists. Review never authors the change it is judging.
This is the canonical review workflow. merge-readiness routes here, and
ai-slop-cleaner is an opt-in lane within it.
Goal
Find what is actually wrong, ranked by severity, with enough detail to act on.
Workflow
- Establish what changed and what it was meant to do.
- Read the change against that intent.
- Check correctness first, then risk, then simplification.
- Verify each candidate finding before reporting it.
- Report findings most-severe first.
What to check
- Correctness — logic defects, edge cases, error paths, concurrency
- Risk — security boundaries, destructive operations, data integrity
- Reuse — existing utilities or patterns the change should have used
- Simplification — code that could be deleted or collapsed
- Coverage — behavior that ships untested
Two axes, run apart
A substantial diff is reviewed as two parallel sub-agent passes, reported separately — never merged or cross-ranked, because a change can pass one axis and fail the other (standards-conforming but wrong behavior; faithful but convention-breaking):
- Standards axis — the diff against the repo's documented standards (CLAUDE.md/AGENTS.md,
docs/standards/volumes where they exist) plus a judgement-call-only smell baseline; anything tooling already enforces is skipped. - Intent axis — the diff against what the work was meant to do — the task, spec, or ticket acceptance criteria: requirements missing or partial, behavior nobody asked for, each finding quoting its source line.
Keep each sub-agent brief under ~400 words and pointed at one axis. Aggregate without picking a single winner across axes — that reranking is what the separation exists to prevent; state each axis's verdict on its own. A small diff stays one pass.
Show full SKILL.md (91 more words)Show less
Rules
- Separate lanes: the reviewer must not be the author's same active context.
- Verify before reporting. A plausible-sounding finding that does not reproduce is noise.
- State severity honestly; do not pad the list to look thorough.
- "No findings" is a valid result when the work is sound.
- Advisory by default — review informs, it does not gate. Hard gates (release, security, destructive operations) stay separate and fail closed.
Output
- Findings, most-severe first, each with file, line, and concrete failure scenario
- What was checked and found clean
- Anything that could not be assessed
© Yeachan-Heo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/review of Yeachan-Heo/oh-my-claudecode.
Open the folder on GitHubat commit 454bae0
Compare with similar skills
OMC Review Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| OMC Review Workflow this skillYeachan-Heo/oh-my-claudecode | 40k | — | ~655 | Automated safety check: Pass | MIT | |
| Main RouterVCnoC/Claude-Code-Zen-mcp-Skill-Work | 116 | — | ~12k | Automated safety check: Pass | Apache-2.0 | |
| Code Reviewaiskillstore/marketplace | 433 | — | ~2.3k | Automated safety check: Pass | None | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Skill Doli Code ReviewDolibarr/dolibarr | 7.7k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Dignified Python Standardsdocling-project/docling | 69k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Code Review
aiskillstore/marketplace
This skill should be used when the user requests a code review of changed files.
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Skill Doli Code Review
Dolibarr/dolibarr
Reviews Dolibarr PHP code for compliance with coding standards and security best practices, and fixes identified issues.
Dignified Python Standards
docling-project/docling
Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance.
Clean Code Guard
amElnagdy/guard-skills
Reviews generated or changed production code against Clean Code, SOLID, DRY, KISS, YAGNI and LLM-specific failure modes before it ships, in any language.
More from Yeachan-Heo/oh-my-claudecode
All 47 skills in this repoAsk Advisor Routing
Yeachan-Heo/oh-my-claudecode
Sends a question or task to another locally installed agent CLI, such as Codex or Gemini, through omc ask and saves the answer as a file.
Ask Navigator
Yeachan-Heo/oh-my-claudecode
Charts a foggy effort into a map of decision tickets on the repo's issue tracker and works through them one per session, producing decisions rather than deliverables.
Self-Improve Evolutionary Loop
Yeachan-Heo/oh-my-claudecode
Runs an autonomous improvement loop on a repository: agents propose and execute plans, a tournament picks the winner by benchmark, and each round is recorded and plotted.
Autopilot
Yeachan-Heo/oh-my-claudecode
Takes a short product idea through requirements, design, planning, parallel implementation, QA cycles and multi-reviewer validation to produce working code.
OMC Mode Cancellation
Yeachan-Heo/oh-my-claudecode
Detects and gracefully cancels whichever OMC mode, autopilot, ralph, swarm, pipeline, or team, is currently active, then clears its state.
Hierarchical AGENTS.md Generator
Yeachan-Heo/oh-my-claudecode
Maps a codebase directory by directory and writes linked AGENTS.md files, each pointing to its parent, to document what each area contains.
Related
Categories
Questions about OMC Review Workflow
What does OMC Review Workflow do?
Reviews finished work for correctness, risk, reuse and simplification, and reports verified findings most severe first without authoring the change. Review evaluates work that already exists and never writes the change it is judging. The agent establishes what changed and what it was meant to do, reads the change against that intent, checks correctness first, then risk, then simplification, and verifies each candidate finding before reporting it.
When should I use OMC Review Workflow?
OMC Review Workflow fits situations like: reviewing a finished change before it ships; checking a diff against both repo standards and the original ticket; looking for risky or unnecessary code in work another agent wrote.
How do I install OMC Review Workflow in Claude Code?
Run `npx skills add Yeachan-Heo/oh-my-claudecode --skill omc-review -a claude-code`. Or copy the skill folder (skills/review in Yeachan-Heo/oh-my-claudecode) into .claude/skills/omc-review in your project. Claude Code loads it when a task matches its description.
How do I install OMC Review Workflow in Codex?
Run `npx skills add Yeachan-Heo/oh-my-claudecode --skill omc-review -a codex`. Or copy the skill folder (skills/review in Yeachan-Heo/oh-my-claudecode) into .agents/skills/omc-review in your project. Codex loads it when a task matches its description.
Can I use OMC Review Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Yeachan-Heo/oh-my-claudecode --skill omc-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omc-review, .gemini/skills/omc-review, .github/skills/omc-review and .opencode/skills/omc-review in your project.
What does OMC Review Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: OMC Review Workflow is instructions for the agent only.
Does OMC Review Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is OMC Review Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does OMC Review Workflow use?
OMC Review Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does OMC Review Workflow use?
About 655 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to OMC Review Workflow?
Skills that share tags, products or a category with OMC Review Workflow: Main Router (VCnoC/Claude-Code-Zen-mcp-Skill-Work, 116 stars), Code Review (aiskillstore/marketplace, 433 stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars) and Skill Doli Code Review (Dolibarr/dolibarr, 7.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains OMC Review Workflow?
Yeachan-Heo (a GitHub user) maintains it in Yeachan-Heo/oh-my-claudecode, which has 39,751 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 8, 2026.
Source: Yeachan-Heo/oh-my-claudecode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.