CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Run a comprehensive code review

52

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/code-review/SKILL.md

The canonical home for this skill is code-review in Yeachan-Heo/oh-my-codex

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable review card with concrete commands, prompt templates, a deterministic synthesis gate, and a clear exit condition. Its main weakness is repetition of the independence/no-self-review rule, which inflates length without adding guidance.

Suggestions

Consolidate the three restatements of the unavailable-lane / do-not-self-review rule into one canonical paragraph (e.g. in the Synthesis gate) and reference it from Execution step 2 to trim redundancy.

Make the `task()` invocation examples concrete by replacing the illustrative `task(...)` pseudo-syntax with the actual agent-invocation mechanism used (CLI command or tool call) so they are copy-paste ready.

Resolve the `[scope and artifacts]` placeholder with a one-line instruction on how to interpolate the recorded scope into the lane prompts.

DimensionReasoningScore

Conciseness

The body is mostly lean operational directives (git commands, task() prompts, state contract, output template), but the unavailable-lane / do-not-self-review rule is restated three times (Execution step 2, the Synthesis gate, and a standalone paragraph), matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not 4 because the repetition is more than minor.

3 / 5

Actionability

It supplies concrete `git status`/`git diff` commands, an `omx state write` JSON payload, exact `task()` prompt templates, and a copy-paste report contract, matching 'Mostly executable guidance; concrete code or commands with minor gaps'; not 5 because of `[scope and artifacts]` placeholders and illustrative pseudo-invocation syntax rather than a real CLI.

4 / 5

Workflow Clarity

The process is clearly sequenced (Inputs -> Execution -> taxonomy -> state contract -> synthesis gate -> output contract -> exit condition) with a deterministic gate and an exit-condition checklist, matching 'Clear sequence with most checkpoints present'; not 5 because error-recovery is delegated outward (rework/ralplan) rather than an explicit in-flow validate-fix-retry loop.

4 / 5

Progressive Disclosure

Headers organize the card well and the one external reference (`templates/AGENTS.md`) is clearly signaled at one level deep; no bundle files exist and the self-contained single-file form is appropriate, matching 'Good structure; most content is appropriately placed; references mostly clear'; not 5 because nothing is actually split across files.

4 / 5

Total

15

/

20

Passed

Description

45%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is short and names its domain, but it is generic in action, lacks any explicit use-when trigger guidance, and risks overlapping with neighboring review skills. It reads as a label rather than a scoping trigger.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when the user asks for a code review, merge-readiness check, or quality/security assessment of a diff, commit, or PR.'

Replace the generic verb 'Run' and the buzzword 'comprehensive' with 2-3 concrete actions, e.g. 'Review a diff for spec compliance, security, quality, and maintainability and return severity-rated findings with a merge recommendation.'

Add disambiguating triggers (PR review, merge readiness, pre-merge quality check) and a brief 'do not use for implementation or broad planning' note to reduce overlap with sibling skills.

DimensionReasoningScore

Specificity

"Run a comprehensive code review" names the domain (code review) but offers only one generic action ("run") and a buzzword ("comprehensive"), matching the anchor 'Names the domain but actions are minimal or generic'; it does not enumerate concrete actions, so it stays below 3.

2 / 5

Completeness

It gives a clear 'what' (run a code review) but entirely omits a 'when'/'Use when...' clause, which the guideline caps at 3; matches 'Has a clear what but when is missing or only weakly implied'.

3 / 5

Trigger Term Quality

"code review" is a natural phrase users actually say, but no synonyms or variations (PR review, merge readiness, security assessment, diff review) are present, matching 'Some relevant keywords but missing common variations or synonyms'; not 4 because coverage is a single phrase rather than good breadth.

3 / 5

Distinctiveness Conflict Risk

"code review" is a recognizable niche but overlaps with sibling skills (review, security-review, simplify), matching 'Somewhat specific but could still overlap with similar skills'; not 4 because the bare phrase does not carve out a distinct trigger.

3 / 5

Total

11

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Yeachan-Heo/oh-my-codex
Reviewed

Table of Contents

Is this your skill?

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.