CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-reviewer

Review code changes for concrete behavior, contract, security, test, maintainability, and documentation defects. Use when the user exactly asks you for a "code review" or to "review" code.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 content is a well-engineered instruction-only skill: concrete commands and output templates, a clearly sequenced coordinator workflow with explicit validation and recovery steps, and a clean split between the overview and genuinely useful one-level-deep references. The remaining polish is trimming the repeated staged-only guidance and supplying the one missing worktree command.

DimensionReasoningScore

Conciseness

The body is dense and professional with no re-teaching of concepts Claude already knows (the bash block presents commands without explanation), matching "efficient; minor instances that could be trimmed". It is not 5 because staged-only target rules are repeated across "Establish the Target" and "Coordinator Responsibilities" (and again in investigation.md), and several sentences run very long with stacked qualifiers.

4 / 5

Actionability

Mostly executable guidance: a copy-paste command block covering PR, working tree, branch/commit/range targets, a concrete markdown output template, and explicit severity decision rules (Approve/Request Changes/Comment). It falls short of 5 only on small gaps, e.g. "materialize a temporary review worktree pinned to the target" names the operation without giving the command.

4 / 5

Workflow Clarity

The multi-step process is clearly sequenced (establish target → select mode → prepare neutral facts → dispatch → audit coverage → verify → deduplicate → report) with explicit validation checkpoints ("audit coverage against the target... redispatch for material gaps", "Run a focused non-destructive test, type check, build, linter, or reproduction when it can materially confirm or reject a candidate") and error-recovery loops ("If cleanup would disturb local work, stop and ask"). This matches the top anchor with feedback loops and no missing checkpoints; the destructive-operation cap does not apply since the review is explicitly read-only.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview keeping roles, target establishment, severity policy, and output format inline, while procedure is split into well-signaled, one-level-deep references ([Investigation](references/investigation.md), [Standard Review](references/standard-review.md), [Adversarial Review](references/adversarial-review.md)) — all verified to exist, with review-cues.md reachable one hop from investigation.md. Mode selection is explicitly routed ("Use [Standard Review]... Use [Adversarial Review] only when..."), matching the clear-overview top anchor.

5 / 5

Total

18

/

20

Passed

Description

87%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 a strong example: it states a concrete capability scope, gives an explicit 'Use when' clause with the natural trigger phrases, and narrows triggering precisely to avoid misfires. The only improvement space is adding a few common trigger variations (PR, pull request, diff) and broadening beyond the single review action.

DimensionReasoningScore

Specificity

"Review code changes for concrete behavior, contract, security, test, maintainability, and documentation defects" names the domain and enumerates six specific defect categories, matching the "several specific actions; minor gaps" anchor. It stays at 4 rather than 5 because it rests on a single action verb (review) with the categories as objects, rather than multiple distinct concrete actions.

4 / 5

Completeness

The first sentence clearly states what the skill does (reviews code changes for six named defect classes) and the second explicitly states when with concrete trigger phrases ("Use when the user exactly asks you for a 'code review' or to 'review' code"), matching the top anchor's what+when pattern with explicit triggers.

5 / 5

Trigger Term Quality

"code review" and "review" code capture the most natural trigger phrases, giving good keyword coverage. It is not 5 because common variations users say — "review this PR", "review the diff", "look over my changes" — are absent, and not 3 because the core natural phrases are explicitly present.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (code-change defect review) and the "exactly asks you for a 'code review'" qualifier makes the trigger precise, minimizing overlap with adjacent skills (security review, document review, general code questions). This matches the clear-niche, minimal-conflict anchor.

5 / 5

Total

18

/

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

shillem/cc-marketplace

Path

plugins/code-swiss-knife/skills/code-reviewer/SKILL.md

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.