review-delta

Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/review-delta/SKILL.md

Quality

Content

78%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 content is an efficient, actionable delta-review workflow with concrete tool calls and a clear step sequence, appropriately scoped as a compact single-purpose skill. Its main gap is a templated rather than fully exemplified reporting format and the absence of an explicit error-recovery checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean and action-oriented with concrete tool calls and minimal over-explanation; the 'Advantages Over Full-Repo Review' section is slightly padded marketing-style content that could be trimmed, keeping it just below fully lean.	4 / 5
Actionability	Provides concrete, copy-paste-ready tool invocations with arguments (e.g. get_review_context_tool(), query_graph_tool(pattern="tests_for", target=<function_name>)), but the reporting format in step 5 is a template outline rather than a fully worked example, leaving a minor gap.	4 / 5
Workflow Clarity	A clearly sequenced 1-5 process with concrete tool calls per step; because this is read-only review rather than destructive/batch work, the missing validation feedback loop does not trigger the cap, though no explicit error-recovery checkpoint is present.	4 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, and well-organized into clear sections (Steps, Advantages) with no need for external bundle files, satisfying the simple-skills exception for a top score; it also signals deeper workflow detail via get_docs_section_tool(section_name="review-delta").	5 / 5
	Total	17 / 20 Passed

Description

66%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 is specific and reasonably distinct, naming several concrete capabilities and natural trigger terms, but it omits an explicit 'Use when...' clause, which caps completeness and leaves the trigger guidance implicit rather than stated.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when reviewing only changed code, git diffs, or staged changes rather than the whole repository.'

Include common user synonyms such as 'git diff', 'staged changes', or 'diff' alongside 'changes since last commit' to broaden natural trigger coverage.

Tighten the action list toward enumerated review checks (correctness, style, test coverage) to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ('Review only changes since last commit', 'impact analysis', 'automatic blast-radius detection', 'Token-efficient delta review') with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the comprehensive 5.	4 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural phrases like 'changes since last commit' and 'last commit' appear, but common synonyms users say ('git diff', 'staged changes', 'diff') are missing, placing it just below comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	'delta review' scoped to 'changes since last commit' is a clear niche with distinct triggers, with only minor overlap risk against general full-repo code-review skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: tirth8205/code-review-graph
Path: skills/review-delta/SKILL.md
Commit: b586687

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.