Evaluate finished work for defects, risk, and simplification before it ships
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/review/SKILL.mdUse this skill to evaluate work that already exists. Review never authors the change it is judging.
This is the canonical review workflow. ai-slop-cleaner is an opt-in lane
within it.
Find what is actually wrong, ranked by severity, with enough detail to act on.
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):
docs/standards/ volumes, CONTRIBUTING.md, CODING_STANDARDS.md or equivalents) and review against whatever exists — a standards file you didn't look for is a standard you didn't apply.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.
Before finalizing the review, check the existing merged OMC qualityGates["omc-review"] entries (project stage entries replace the user list; see docs/quality-gates-configuration.md). If there are no entries, do not call omc quality-gates list, spawn gate tasks, or add a Quality Gates section or gate records to the review output. If there is at least one entry, call omc quality-gates list --stage omc-review --json and show every validation error. For each available gate, spawn one independent Claude Code Task that loads the named skill from resolvedPath, reviews the same changes, and returns VERDICT: PASS or VERDICT: BLOCK plus findings. Use the configured model override when present; do not pass another reviewer's output to the gate. Reuse the same gate lane if the change is revised and reviewed again.
When gates are configured, record { gate, mode, verdict } for each gate in a Quality Gates section of the review output. Unresolved skills are gate_unavailable with a visible warning, never PASS; they do not fail the review stage. A blocking BLOCK makes the overall result REQUEST CHANGES; advisory results are informational and never block.
Yeachan-Heo/oh-my-claudecode
453d3de
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.