CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review-checklist

Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability

50

Quality

55%

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 ./skills/code-review-checklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 well-organized and genuinely actionable, with concrete checklists, executable good/bad code examples, and usable comment templates. However, it is roughly three times longer than it needs to be — much of it restates code-review fundamentals Claude already knows — and it keeps all reference material inlined instead of splitting it into bundle files. The escaped nested code fences in the Examples section would also break markdown rendering.

Suggestions

Cut generic knowledge Claude already has (e.g. the 'What if...?' edge-case primer, 'Don't Be Rude', 'Be Constructive') and keep only team- or workflow-specific guidance, targeting a much shorter SKILL.md.

Move the full checklists, example galleries, and review comment templates into separate reference files (e.g. references/checklists.md, references/templates.md) linked one level deep from the body.

Fix the nested code fences in the Examples section — the escaped \`\`\` blocks will render as literal text; use a different fencing strategy (e.g. four-backtick outer fences).

DimensionReasoningScore

Conciseness

At ~450 lines, the body extensively restates code-review knowledge Claude already has (e.g. 'What if the input is null?', 'Don't Be Rude', 'Be Constructive') plus filler like a 'Pro Tip', matching the 'noticeably verbose; several unnecessary explanations or padded sections' anchor. It avoids a 1 only because it is not written as a beginner tutorial explaining basic concepts.

2 / 5

Actionability

The content provides concrete checkbox lists, executable bad/good code pairs (e.g. the parameterized-query and validation examples), and ready-to-use review comment templates, fitting 'mostly executable guidance; concrete code or commands with minor gaps'. It falls short of 5 because the templates are placeholder-only and the nested escaped code fences would not render as intended.

4 / 5

Workflow Clarity

The six review steps are clearly sequenced (Understand Context through Review Tests) and the Pre-Review checklist includes checkpoints like 'Check if tests pass in CI/CD' and 'Pull the branch and run it locally', matching 'clear sequence with most checkpoints present'. It is not a 5 because there are no explicit validate-fix-retry feedback loops, and not a 3 since checkpoints are present rather than implicit.

4 / 5

Progressive Disclosure

The body is well-sectioned with headers, but it is monolithic: full checklists, example galleries, and comment templates that clearly belong in separate reference files are all inlined in one ~450-line SKILL.md, and no bundle files exist. This fits 'some structure but content that should be separate is inline'.

3 / 5

Total

13

/

20

Passed

Description

53%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 clearly communicates the skill's domain and scope but is generic: it lists review categories rather than concrete actions, omits natural trigger phrases like 'pull request' or 'PR', and entirely lacks a 'Use when...' clause. It sits at the midpoint of quality — informative but not yet trigger-optimized.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reviewing pull requests, conducting code audits, or establishing team code review standards.'

Replace the category list with concrete actions, e.g. 'Guides systematic review of code for bugs, security flaws, performance issues, and maintainability.'

Include natural user phrasings such as 'pull request', 'PR review', and 'code audit' to improve trigger matching.

DimensionReasoningScore

Specificity

Names the domain ("conducting thorough code reviews") and enumerates four coverage areas ("functionality, security, performance, and maintainability"), but these are topics rather than concrete actions, matching the 'names domain and 1-2 concrete actions' anchor rather than the 'several specific actions' level.

3 / 5

Completeness

The description gives a clear 'what' ("comprehensive checklist for conducting thorough code reviews") but contains no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"code reviews" is a natural keyword users would say, but common variations like "pull request", "PR review", or "code audit" are missing, fitting the 'some relevant keywords but missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

The code-review niche with enumerated categories is mostly distinguishable from unrelated skills, with only minor overlap risk against closely related review/feedback skills; it lacks the distinct trigger phrases needed for a 5.

4 / 5

Total

13

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/agentic-awesome-skills
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.