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

The canonical home for this skill is speckit-git-feature in unoplatform/uno

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 body is a well-organized, actionable instruction skill with concrete Bash/PowerShell commands, a sequenced workflow, and graceful degradation. The main gaps are non-deterministic short-name generation and the absence of an explicit failure-retry loop.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence (no explanation of git/branching basics) and is mostly lean with purposeful sections, though the IMPORTANT block and env-var override detail could be trimmed slightly, matching the "efficient; minor instances of over-explanation" anchor.	4 / 5
Actionability	Concrete, copy-paste-ready script invocations with explicit flags are given for both Bash and PowerShell, but the short-name generation is left as prose guidance ("Generate a concise short name (2-4 words)") rather than a deterministic step, a minor gap keeping it below 5.	4 / 5
Workflow Clarity	A clear ordered sequence exists (prereq git check -> numbering-mode determination -> execute -> parse output) with an explicit git-availability checkpoint and graceful-degradation handling, but there is no explicit validate/retry loop on script failure, matching the "clear sequence with most checkpoints; minor validation gaps" anchor.	4 / 5
Progressive Disclosure	The skill is a single self-contained file with clear section headers and no nested references, and no bundle files exist to split into; it is just over the 50-line simple-skill threshold with inlined detail that could arguably live in references, so it lands at 4 rather than 5.	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 clear and concrete about what the skill does but omits any explicit "when to use it" trigger guidance, which caps completeness and limits trigger-term coverage. It is mostly distinct from sibling skills thanks to the numbering qualifier.

Suggestions

Add a "Use when..." clause naming the trigger (e.g., "Use when starting a new spec-driven feature that needs a numbered git branch").

Broaden trigger terms with synonyms users actually say (e.g., "git branch", "new branch", "checkout feature branch").

Optionally note both numbering modes as distinct capabilities to lift specificity above a single action.

Dimension	Reasoning	Score
Specificity	"Create a feature branch" is a concrete action and "with sequential or timestamp numbering" names the variant, but only one action with two numbering modes is covered — not comprehensive, matching the anchor that names a domain with 1-2 concrete actions.	3 / 5
Completeness	It clearly states the "what" (create a numbered feature branch) but has no "Use when..." or equivalent trigger guidance; the rubric explicitly caps completeness at 3 when the "when" is missing, so it cannot reach 4.	3 / 5
Trigger Term Quality	"feature branch" is a natural term a user would say, but coverage stops there with no synonyms or variations (e.g., "git branch", "checkout", "new branch"), matching the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The "sequential or timestamp numbering" qualifier gives it a clear niche within git workflows with only minor overlap risk against generic git-branch skills, matching the "mostly distinct" anchor rather than the broader score-3.	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: mixpanel/mixpanel-headless
Path: .claude/skills/speckit-git-feature/SKILL.md
Commit: 1ccd7ae

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.