CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-changes

Perform a structured code review using change detection and impact

Quality

78%

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

Quality

Content

93%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 a tight, highly actionable instruction skill with concrete parameterized tool calls and a clear sequenced workflow. The only gap is the absence of an explicit validation/feedback-loop checkpoint in the review workflow.

Suggestions

Add an explicit validation checkpoint between analysis and output (e.g. 'Before writing findings, re-confirm each high-risk function's test coverage via step 3') to support error recovery.

Optionally clarify the merge recommendation criteria (e.g. what risk/coverage threshold maps to 'approve' vs 'request changes').

DimensionReasoningScore

Conciseness

The body is lean and efficient, assumes Claude's competence ('The graph narrows scope; it does not replace the source'), and every line earns its place with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Guidance is fully actionable: each step names a concrete tool with specific parameters (e.g. `query_graph_tool` with `pattern="tests_for"`, `detail_level="minimal"`), covering the common cases of a review task.

5 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced with explicit conditional gating ('only when you need the steps', 'when the blast radius is not clear from step 1'), but there is no explicit validation/feedback loop checkpoint for error recovery.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no external bundle files (references/, scripts/, assets/ all empty) and is organized into clearly labeled sections (Steps, Output Format, Token Efficiency Rules), meeting the simple-skill exception for a top score.

5 / 5

Total

19

/

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 uses correct third-person voice and names a specific niche, but it omits any 'Use when...' trigger guidance and lacks synonyms that users naturally say. Adding an explicit trigger clause would lift the completeness and trigger-term dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when reviewing a change set, pull request, or staged diff and you need risk scores and blast radius.'

Add natural synonyms users say — 'review my code', 'PR review', 'review the diff' — alongside 'code review'.

List a couple more concrete review actions (e.g. 'flag untested high-risk functions', 'recommend merge/reject') to round out specificity.

DimensionReasoningScore

Specificity

The description names the domain ('structured code review') and two concrete actions ('change detection' and 'impact') but stops short of comprehensive coverage of review activities.

3 / 5

Completeness

There is a clear 'what' ('Perform a structured code review using change detection and impact') but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

'code review' is a natural term users would say, but the description misses common synonyms and trigger variations like 'review my changes', 'PR review', or 'review the diff'.

3 / 5

Distinctiveness Conflict Risk

The knowledge-graph-based 'change detection and impact' framing carves a distinct niche, with only minor overlap risk against closely related generic review skills.

4 / 5

Total

13

/

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

tirth8205/code-review-graph

Path

skills/review-changes/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.