speckit-git-initialize

Initialize a Git repository with an initial commit

1.26x

Quality

48%

Does it follow best practices?

Impact

90%

1.26x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/speckit-git-initialize/SKILL.md

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides clear, actionable guidance for initializing a Git repository with good fallback handling. Its main weaknesses are the inclusion of unnecessary customization suggestions that Claude already knows about, and the lack of an explicit verification step after the initialization process completes. The structure is adequate but could benefit from trimming and adding a post-init validation check.

Suggestions

Add a verification step after initialization, e.g., 'Verify: run `git log --oneline` to confirm the initial commit was created successfully'

Remove or significantly trim the Customization section — Claude already knows about .gitignore, branch naming, LFS, hooks, etc. A single line like 'Customize the script for project-specific Git setup needs' would suffice

Trim the Graceful Degradation section to be more concise — the behavioral details about skipping and continuing are already implied by the script handling checks internally

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some unnecessary sections. The 'Customization' section lists generic Git features Claude already knows about, and the 'Graceful Degradation' section explains behavior that's already handled by the scripts internally. These could be trimmed.	2 / 3
Actionability	Provides concrete, executable commands for both Bash and PowerShell, with clear fallback commands. The script paths are specific and the fallback git commands are copy-paste ready.	3 / 3
Workflow Clarity	The workflow is straightforward (run script or fallback commands), but there's no explicit validation checkpoint after initialization. The error handling section mentions stopping on failure but doesn't provide a verification step (e.g., checking `git log` after commit). For a potentially destructive operation (initial commit of all files), a validation step would be appropriate.	2 / 3
Progressive Disclosure	The content is reasonably organized with clear sections, but the Customization section lists items that could be in a separate reference file. Without bundle files, the references to extension scripts at `.specify/extensions/git/scripts/` cannot be verified, and there are no links to supporting documentation.	2 / 3
	Total	9 / 12 Passed

Description

32%

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 brief, single-action statement that identifies the core task but lacks depth. It is missing a 'Use when...' clause, which is critical for skill selection, and doesn't include enough trigger term variations to reliably match user requests. The description would benefit significantly from explicit trigger guidance and additional natural keywords.

Suggestions

Add a 'Use when...' clause with trigger terms like 'git init', 'new repo', 'set up repository', 'start a new project with git', 'first commit'.

Expand the description to list more specific actions, e.g., 'Creates a new Git repository, sets up .gitignore, and makes an initial commit with a standard message.'

Include common user phrasings and file references such as 'new project', 'start tracking files', '.git', 'initialize version control'.

Dimension	Reasoning	Score
Specificity	Names a specific domain (Git) and two actions (initialize a repository, make an initial commit), but doesn't list additional concrete actions or details beyond the basic task.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also minimal, warranting a 1.	1 / 3
Trigger Term Quality	Includes 'Git repository' and 'initial commit' which are relevant keywords, but misses common variations like 'git init', 'new repo', 'set up a repo', 'first commit', or '.git'.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to Git initialization, but could overlap with broader Git skills or repository management skills. The narrow scope helps somewhat, but the lack of explicit boundaries increases conflict risk.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: mixpanel/mixpanel-headless
Commit: fd7b9ba

Reviewed: 27 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.