speckit-git-feature

Create a feature branch with sequential or timestamp numbering

Quality

64%

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-feature/SKILL.md

Quality

Content

75%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 well-structured, actionable, and concise with a clear workflow and validation checkpoint. Trimming the short-name guidance and tightening placeholder handling would push it toward top marks.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational with no padding about concepts Claude already knows; only minor over-explanation in the short-name generation bullets keeps it from a 5.	4 / 5
Actionability	It gives exact copy-paste Bash and PowerShell commands with required flags (--json/-Json), though the placeholder args (<short-name>, <feature description>) leave a small gap from fully ready-to-run.	4 / 5
Workflow Clarity	A clear sequence (prereq check → numbering mode → short name → run script → output) with an explicit git-availability checkpoint and graceful-degradation fallback; branch creation is not destructive/batch so the cap-3 does not apply.	4 / 5
Progressive Disclosure	No bundle files exist, and the body is organized into well-labeled sections; it sits just over the ~50-line simple-skill threshold and references external project script paths rather than bundle references, so a 5 is not fully earned.	4 / 5
	Total	16 / 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 is specific and distinguishable but lacks any trigger/usage guidance, capping its completeness. Adding a "Use when..." clause naming natural user phrases would lift the two weakest dimensions.

Suggestions

Append a trigger clause such as "Use when starting work on a new spec-kit feature and you need a numbered feature branch."

Add natural synonyms users might say, e.g. "git branch", "new branch", or "spec branch", to broaden trigger-term coverage.

Consider mentioning the branch-name format output (e.g. "003-user-auth") so the "what" is more concrete.

Dimension	Reasoning	Score
Specificity	"Create a feature branch" names the domain and one concrete action with its two numbering variants ("sequential or timestamp numbering"), but offers only that single action rather than a comprehensive set.	3 / 5
Completeness	The description gives a clear "what" but no "when"/Use-when clause; per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	"feature branch" is a natural term a user would say, but there are few synonyms (e.g. "git branch", "new branch") and no explicit trigger phrase, so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	"feature branch with sequential or timestamp numbering" is a specific niche with minimal overlap, though it could be confused with general git-branch skills.	4 / 5
	Total	13 / 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-feature/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.