CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review

Use when the user asks to "review code", "review my changes", "code review", "review this PR", "review pull request", "check code quality", "review this file", "review this diff", or wants feedback on code changes, code quality, or best practices.

Quality

82%

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

82%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 strong, highly actionable skill body: concrete commands, explicit tool names, hard testing rules, and a complete output format. Its weaknesses are minor — a duplicated 'read the full file' instruction across Steps 1 and 2, and no explicit validation/feedback checkpoint on the final review output.

DimensionReasoningScore

Conciseness

Imperative and lean throughout with no concept explanations, but Step 1's 'Always read the full file content for each changed file' is duplicated verbatim in Step 2 ('Read the full file for each changed file, not just the diff') — minor trimmable redundancy.

4 / 5

Actionability

Copy-paste-ready commands for every scope path ('git diff --cached', 'git diff main...HEAD', 'gh pr diff <number>', 'gh api repos/{owner}/{repo}/releases/latest'), exact MCP tool names, a complete output template with per-issue format, and quantified criteria ('>= 80% code coverage', 'never latest'). Fully executable guidance with no missing key details.

5 / 5

Workflow Clarity

A clear 5-step numbered sequence with each step's sub-decisions enumerated and a conditional branch ('If SonarQube MCP tools are not available, skip this step silently'). Falls short of 5 because there is no explicit validation checkpoint or feedback loop on the produced review.

4 / 5

Progressive Disclosure

No bundle files exist; the body is well-organized with clear section headers and each section self-contained. The inline output template is core content that belongs in SKILL.md, though at ~110 lines with a bulky template block there are minor organization gaps versus the ideal split.

4 / 5

Total

17

/

20

Passed

Description

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

An excellent trigger-focused description with comprehensive natural phrases, but it is all 'when' and almost no 'what'. Adding an explicit capability statement (e.g., 'Reviews code changes and produces a structured report of critical issues, warnings, and suggested fixes') would make it complete.

Suggestions

Lead with a one-clause capability statement in third person (e.g., 'Reviews code changes for bugs, security issues, and test coverage gaps, and produces a structured review with suggested fixes') before the 'Use when' trigger list.

Trim overlapping soft triggers like 'best practices' or 'check code quality' if they risk matching linting/formatting skills, or make them more specific (e.g., 'review code quality issues in a diff').

DimensionReasoningScore

Specificity

The description names the code-review domain but the only actions are quoted trigger phrases ('review code', 'check code quality') — it never states concrete capabilities like 'produces categorized findings with suggested fixes'. Fits 'names domain and 1-2 concrete actions, but not comprehensive'.

3 / 5

Completeness

'When' is fully explicit with concrete trigger phrases, but 'what' is only implied through those phrases ('feedback on code changes, code quality, or best practices') rather than stated as a capability. Both present; the 'what' could be more explicit.

4 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say: 'review code', 'review my changes', 'code review', 'review this PR', 'review pull request', 'check code quality', 'review this file', 'review this diff'. Covers synonyms and variations with essentially no gaps.

5 / 5

Distinctiveness Conflict Risk

'Code review', 'review this PR', 'review this diff' form a distinct niche, but 'check code quality' and 'best practices' create minor overlap risk with linting, formatting, and security-review skills.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

adityamparikh/code-review-skill

Path

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.