CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

87

1.25x
Quality

Does it follow best practices?

Impact

85%

1.25x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A well-structured, actionable guide with clear sequenced phases and concrete templates, but it is a monolithic 525-line document with repetition and no external references to offload detail. Tightening prose and splitting large reference material into bundle files would lift the weaker dimensions.

Suggestions

Move the language-specific code patterns (Python, TypeScript) and the full security/test checklists into references/ files (e.g., LANGUAGE-PATTERNS.md, CHECKLISTS.md) and link to them one level deep from the body.

De-duplicate the security checklist that appears in both 'Technique 1: The Checklist Method' and 'Pattern 3: Security Review', keeping one inline and pointing to a single reference.

Trim the 'Core Principles' section's obvious goal lists (e.g., 'Catch bugs and edge cases', 'Show off knowledge') to only what adds non-obvious guidance beyond Claude's existing knowledge.

DimensionReasoningScore

Conciseness

The 525-line body is mostly useful but padded: security checklists appear twice (Technique 1 and Pattern 3) and the 'Core Principles' section restates obvious review goals Claude already knows, so it could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready artifacts — good/bad feedback examples, a PR Review Comment Template, severity labels (🔴/🟡/🟢), and executable language-specific code patterns — meeting the bar for specific examples.

3 / 3

Workflow Clarity

The Review Process is clearly sequenced into Phase 1–4 with time estimates and a decision checkpoint (Approve/Comment/Request Changes), plus checklists for complex steps; no validation cap applies since review is non-destructive.

3 / 3

Progressive Disclosure

At 525 lines with no bundle files, content that should be split (language-specific patterns, detailed checklists, templates) is all inline, matching the anchor where content that should be separate remains inline rather than in one-level-deep references.

2 / 3

Total

10

/

12

Passed

Description

100%

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 description that concisely states concrete capabilities and provides an explicit 'Use when' trigger clause with natural terms. It is distinguishable from other skills and free of first/second-person voice.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'provide constructive feedback, catch bugs early, and foster knowledge sharing' — rather than vague language, matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Master effective code review practices to provide constructive feedback...') and when via the explicit 'Use when reviewing pull requests, establishing review standards, or mentoring developers' clause.

3 / 3

Trigger Term Quality

Includes natural terms a user would actually say — 'reviewing pull requests', 'establishing review standards', 'mentoring developers' — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear 'code review' niche with distinct triggers ('reviewing pull requests', 'mentoring developers') unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (530 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
wshobson/agents
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.