Agent Skills
› Yeachan-Heo/oh-my-claudecode
› omc-review
omc-review
GitHub用于评估已完成工作的缺陷、风险和简化空间，在发布前进行代码审查。通过检查正确性、风险、复用性和覆盖率，按严重程度报告发现的问题，确保工作质量。
Trigger Scenarios
代码合并前审查
功能开发完成后验证
安全或破坏性操作风险评估
Install
npx skills add Yeachan-Heo/oh-my-claudecode --skill omc-review -g -y
SKILL.md
Frontmatter
{
"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
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
Version History
- 74e4e11 Current 2026-08-28 11:12
