CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review-excellence

Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

65

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 solidly structured skill with an explicit phased workflow, concrete templates, and exemplary use of one-level-deep references. Its main weakness is token efficiency: much of the checklist content is generic knowledge Claude already possesses and could be trimmed or moved to references.

Suggestions

Trim the generic checklists (off-by-one, N+1, null checks, linters) that Claude already knows, or condense them into the existing reference files, keeping only project- or team-specific guidance in SKILL.md.

Remove or drastically shorten the 'When to Use This Skill' section, which duplicates the frontmatter description almost verbatim.

Add an explicit re-review checkpoint in Phase 4 covering what to do after the author addresses requested changes, closing the workflow's only validation gap.

DimensionReasoningScore

Conciseness

The body includes substantial generic knowledge Claude already has ('Off-by-one errors? Null/undefined checks?', 'N+1 queries?', 'Review Promptly: Within 24 hours') and a 'When to Use This Skill' section that mostly restates the description. Structured and readable, but noticeably padded.

3 / 5

Actionability

Concrete, ready-to-use material: good/bad feedback rewrites, a worked 'Context + Specific Issue + Helpful Solution' example, and a full PR review comment template. Some checklist bullets remain generic ('Are there tests?', 'Clear variable names?').

4 / 5

Workflow Clarity

Four review phases are explicitly sequenced with time budgets and checkpoints (PR-size check, CI status check), ending in an explicit decision step. Minor gap: no re-review loop after changes are requested.

4 / 5

Progressive Disclosure

The body is a well-organized overview; detailed language-specific patterns and interaction techniques are split into two real one-level-deep reference files, each clearly signaled at its point of use with a summary of its contents.

5 / 5

Total

16

/

20

Passed

Description

83%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 well-crafted description that clearly states capabilities and explicit trigger conditions in third person. Keyword coverage is good but lacks synonyms and variations that would make triggering fully comprehensive.

DimensionReasoningScore

Specificity

Names several concrete actions ('provide constructive feedback', 'catch bugs early', 'foster knowledge sharing', 'maintaining team morale') with only minor coverage gaps, though 'Master effective code review practices' is generic framing.

4 / 5

Completeness

Explicitly answers both 'what' (constructive feedback, catching bugs early, knowledge sharing, morale) and 'when' with concrete trigger phrases ('Use when reviewing pull requests, establishing review standards, or mentoring developers').

5 / 5

Trigger Term Quality

'reviewing pull requests', 'establishing review standards', and 'mentoring developers' are natural user phrases, but common variations like 'PR', 'review feedback', or 'diff review' are missing.

4 / 5

Distinctiveness Conflict Risk

Code review is a distinct niche with specific triggers, but the broad 'code review' domain has minor overlap risk with closely related diff-review or review-automation skills.

4 / 5

Total

17

/

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

wshobson/agents

Path

plugins/developer-essentials/skills/code-review-excellence/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.