CtrlK
BlogDocsLog inGet started
Tessl Logo

review

Review code changes for security, performance, bugs, and quality. Reviews staged changes, unstaged changes, specific commits, or PR-ready diffs.

67

Quality

80%

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 ./src/resources/skills/review/SKILL.md
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 highly actionable, well-sequenced review workflow with explicit validation and a decision gate, but it is a monolithic file with some internal repetition that could be tightened or split out.

Suggestions

De-duplicate the read-only rule by stating it once and referencing it, and define severity levels in a single place to remove repetition.

Consider moving the detailed review-category checklists and the full output-format template into a reference file (e.g. references/CATEGORIES.md) referenced from the body, to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of basic-concept filler, but it repeats guidance (the read-only 'DO NOT MODIFY CODE' rule appears in three places and severity levels are defined in both format_findings and output_format), so it could be tightened.

2 / 3

Actionability

It provides concrete, copy-paste-ready guidance: exact git commands per scope, a structured finding template, severity definitions, and specific issue checklists — matching the 'fully executable; specific examples' anchor.

3 / 3

Workflow Clarity

The quick_start sequences determine_review_scope → gather_context → review_categories → format_findings with an explicit validation checkpoint (stop if the diff is empty) and a mandatory decision-gate feedback loop, satisfying the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

The skill is a single ~180-line file with no bundle references; while it is well-organized into tagged sections, large reference-style content (the detailed category checklists, output format) stays inline with no file-level split, matching the 'content that should be separate is inline' anchor.

2 / 3

Total

10

/

12

Passed

Description

82%

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 concise, third-person description with strong specificity and natural trigger terms, but it omits an explicit 'Use when...' clause so the 'when to use' guidance is only implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to review a diff, staged/unstaged changes, a specific commit, or PR-ready changes.'

Consider adding common phrasings users say ('code review', 'review my PR', 'check these changes before committing') to strengthen trigger coverage.

DimensionReasoningScore

Specificity

The description names concrete actions across both review focus areas ('security, performance, bugs, and quality') and review scopes ('staged changes, unstaged changes, specific commits, or PR-ready diffs'), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly answers 'what' the skill does but lacks an explicit 'Use when...' trigger clause; per the guidelines a missing explicit trigger caps completeness at 2 even though the 'when' is implied by the listed scopes.

2 / 3

Trigger Term Quality

Terms like 'review code changes', 'staged changes', 'commit', and 'PR-ready diffs' are natural phrases a user would say when requesting a review, giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The git-diff review framing (staged/unstaged/commit/PR) carves a clear niche unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

11

/

12

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
gsd-build/gsd-2
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.