CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Code review practices with technical rigor and verification gates. Practices: receiving feedback, requesting reviews, verification gates. Capabilities: technical evaluation, evidence-based claims, PR review, subagent-driven review, completion verification. Actions: review, evaluate, verify, validate code changes. Keywords: code review, PR review, pull request, technical feedback, review feedback, completion claim, verification, evidence-based, code quality, review request, technical rigor, subagent review, code-reviewer, review gate, merge criteria. Use when: receiving code review feedback, completing major features, making completion claims, requesting systematic reviews, validating before merge, preventing false completion claims.

75

Quality

92%

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.

A well-structured instruction skill with concrete commands, clear sequenced verification workflows, and clean progressive disclosure into three reference files. The main weakness is moderate redundancy where trigger lists and the closing summary restate content already covered in the protocol sections.

Suggestions

Remove the 'When to Use This Skill' trigger sub-lists that are duplicated in each protocol section, or collapse them to a single canonical trigger block referenced once.

Drop or shrink the 'Bottom Line' section since it restates the three practices already enumerated in Overview and Core Principle.

Inline the one-line subagent dispatch invocation (Task tool + code-reviewer type) so the requesting-review protocol is fully executable without opening the reference.

DimensionReasoningScore

Conciseness

Bullet-driven and assumes Claude knows git/PRs with no concept padding, but triggers repeat across 'When to Use' and the three protocol sections, and 'Bottom Line' restates the three practices — minor trimming available.

4 / 5

Actionability

Provides concrete git SHA commands, a specific subagent dispatch template with named fields, and explicit pass/fail criteria; minor gap is that full dispatch detail is deferred to references.

4 / 5

Workflow Clarity

Verification gate is sequenced IDENTIFY→RUN→READ→VERIFY→THEN claim with a 'skip = lying' rule, a red-flags STOP list, and decision-tree routing to run verification first — explicit validation checkpoints throughout.

5 / 5

Progressive Disclosure

Overview in SKILL.md points to three real, clearly-signaled one-level-deep reference files ('Reference:' / 'Full protocol:' labels), all verified to exist, with content appropriately split.

5 / 5

Total

18

/

20

Passed

Description

100%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.

A strong, well-structured description that explicitly covers what the skill does, when to use it, and natural trigger terms with synonyms. Its only weakness is verbosity: it enumerates Practices, Capabilities, Actions, and Keywords separately, which could be tightened without losing information.

Suggestions

Consolidate the Practices/Capabilities/Actions lists into a single concrete-action sentence to reduce redundancy, since 'Actions' largely restates 'Practices' and 'Capabilities'.

Trim the Keywords list to the highest-signal natural terms; the current ~16 keywords risk noise without adding trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'review, evaluate, verify, validate code changes' and 'receiving feedback, requesting reviews, verification gates' — with comprehensive coverage, matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' (Practices/Capabilities/Actions) and 'when' ('Use when: receiving code review feedback, completing major features, making completion claims...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural keyword coverage including synonyms ('code review, PR review, pull request') plus specific terms like 'completion claim', 'review gate', and 'code-reviewer', matching the score-5 anchor.

5 / 5

Distinctiveness Conflict Risk

Targets a distinct niche — review practices and verification gates rather than generic review — with specific triggers like 'completion claim' and 'verification gate' that minimize wrong-skill conflict.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
samhvw8/dot-claude
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.