speckit-git-feature

Create a feature branch with sequential or timestamp numbering

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/speckit-git-feature/SKILL.md

Quality

Content

88%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-structured, actionable guide with concrete multi-shell commands and a validation feedback loop. Its main weakness is internal inconsistency: the description and the final Output section reference sequential/timestamp/numeric prefixes that the Mandatory Branch Naming section explicitly disables, which is misleading despite the otherwise clean workflow.

Suggestions

Reconcile the Output section's examples (003-user-auth, 20260319-143022-user-auth) with the disabled numbering scheme so BRANCH_NAME/FEATURE_NUM examples match the actual v1/feat/PROJECTCODE-TASK_NUMBER-slug format.

De-duplicate the branch-name format and example string, which currently appear in three places, to tighten the token budget.

Add a one-line note clarifying that the referenced scripts live in the host spec-kit project (not bundled with this skill) so the reader knows where to find them.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and assumes git competence, but the branch-name format and example string recur in several sections and the trailing Output section restates disabled numeric/timestamp prefixes, which could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready Bash and PowerShell invocations with exact env-var assignment, script paths, and JSON flags, covering the common execution cases concretely.	5 / 5
Workflow Clarity	The flow is explicitly sequenced (prerequisites → resolve inputs → compose name → execute → validate) with an explicit regex validation checkpoint and an abort-on-mismatch feedback loop plus graceful degradation.	5 / 5
Progressive Disclosure	A self-contained single file with clearly labeled sections and no nested references; minor gaps remain since some content (e.g., the contradictory Output section) is redundant rather than split or trimmed.	4 / 5
	Total	18 / 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 a minimal single-sentence statement of purpose: it conveys what the skill does but omits any explicit trigger guidance and uses only one natural keyword. It also advertises 'sequential or timestamp numbering', which the body explicitly disables, creating a mismatch. It sits at the midpoint across all dimensions.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when starting a new feature task that needs a Trello-numbered git branch'.

Expand the action list beyond 'Create' to reflect the actual workflow (resolve Trello inputs, compose a conventional-commit branch name, validate).

Correct the numbering claim to match the skill's real behavior, since sequential/timestamp numbering is disabled in the body.

Dimension	Reasoning	Score
Specificity	The description names the domain ('feature branch') and one concrete action ('Create') plus a numbering modifier, but offers only a single action with no broader coverage.	3 / 5
Completeness	It states a clear 'what' (create a feature branch with numbering) but includes no 'Use when...' trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	'feature branch' is a natural term users would say, but common variations like 'git branch', 'new branch', or 'branch naming' are absent, leaving keyword coverage partial.	3 / 5
Distinctiveness Conflict Risk	The phrase is somewhat specific to feature branches but is generic enough to overlap with other git/branch skills; the numbering modifier adds only mild distinctiveness.	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: g14wx/staffSync
Path: .agents/skills/speckit-git-feature/SKILL.md
Commit: 682bfbc

Reviewed: 1 day 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.