speckit-git-validate

Validate current branch follows feature branch naming conventions

Quality

71%

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 ./.claude/skills/speckit-git-validate/SKILL.md

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, fully executable read-only validation skill with clear sequencing and a graceful-degradation fallback. Its only gap is the absence of an explicit error-recovery feedback loop, which is not strictly required for a non-destructive check.

Dimension	Reasoning	Score
Conciseness	The body is lean with no over-explanation of git concepts; every line (prerequisite check, regex patterns, exact output strings, fallback) earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.	5 / 5
Actionability	It provides fully executable commands (`git rev-parse --abbrev-ref HEAD`), exact regex patterns, literal output strings, and an env-var fallback, covering on/off-branch and git-missing cases in copy-paste-ready form.	5 / 5
Workflow Clarity	The flow is clearly sequenced (prerequisite git check → branch lookup → pattern match → execution branches → graceful degradation) with an explicit guard checkpoint, but it is a one-shot validation without a validate→fix→retry loop, so it sits just below the explicit-feedback-loop level of 5.	4 / 5
Progressive Disclosure	This is a single-purpose skill under 50 lines with no bundle files, organized into clear sections (Prerequisites, Validation Rules, Execution, Graceful Degradation), which per the simple-skills note warrants a 5.	5 / 5
	Total	19 / 20 Passed

Description

50%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 clear and concrete about what the skill does but omits any 'when to use' trigger guidance and lacks the spec-kit/naming-pattern specifics that would distinguish it. It sits at the midpoint across all dimensions.

Suggestions

Add a 'Use when...' clause naming the trigger context, e.g. 'Use when working in a spec-kit project and checking that the current Git branch follows feature-branch naming conventions.'

Include the natural trigger terms users would say ('git branch', 'branch name', 'spec-kit feature branch') to improve trigger_term_quality.

Mention the concrete naming patterns (e.g. sequential '001-' or timestamp '20260319-143022-') to raise specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase 'Validate current branch follows feature branch naming conventions' names the domain (git branch validation) and one concrete action (validate naming conventions), but lists no further specific actions, matching the '1-2 concrete actions' anchor rather than the 'several specific actions' of 4.	3 / 5
Completeness	It clearly states the 'what' (validate branch naming) but provides no 'Use when...' or equivalent 'when' guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Terms like 'branch', 'feature branch', and 'naming conventions' are relevant but common user variations ('git branch', 'branch name', 'spec-kit') are missing, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The branch-validation niche is somewhat specific, but omitting spec-kit context and the actual naming patterns leaves overlap risk with generic git branch skills, matching the 'somewhat specific but could still overlap' anchor.	3 / 5
	Total	12 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: unoplatform/uno
Path: .claude/skills/speckit-git-validate/SKILL.md
Commit: eaa505e

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.