speckit-git-commit

Auto-commit changes after a Spec Kit command completes

Quality

66%

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

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

Quality

Content

80%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 lean, highly actionable, and well-structured for a simple single-purpose skill, with copy-paste-ready commands and config. The main gap is workflow clarity: as a batch/destructive git operation it lacks an explicit post-commit verification checkpoint, which the rubric caps at 3.

Suggestions

Add an explicit verification step after committing, e.g. run `git rev-parse --short HEAD` or check `git status` is clean, to confirm the commit succeeded before reporting completion.

Add a checkpoint to verify staged changes were actually committed (exit-code / commit-count check) so the workflow can react to a failed commit rather than silently proceeding.

Tighten the numbered Behavior list by collapsing the event-name lookup steps to reduce mild redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized with no concept padding and every section earning its place; it falls just short of a 5 because the numbered Behavior list restates hook-event logic that could be tightened slightly.	4 / 5
Actionability	It provides concrete, copy-paste-ready executable commands (Bash and PowerShell script paths with the event-name argument) and a complete YAML config example with default-message fallback, fully covering the common cases.	5 / 5
Workflow Clarity	A clear sequence is present and the Graceful Degradation section lists skip conditions, but this is a batch/destructive operation (`git add .` + `git commit`) with no validation checkpoint confirming the commit succeeded; per the rubric, missing validation in batch/destructive workflows caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	Under 50 lines with no bundle files, the skill uses well-organized sections (Behavior, Execution, Configuration, Graceful Degradation); per the simple-skill exception, this satisfies progressive disclosure fully without external references.	5 / 5
	Total	17 / 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 well-scoped to the Spec Kit niche with one concrete action, but it lacks an explicit 'Use when' trigger clause and a fuller list of actions, which cap its specificity and completeness at the midpoint. It is distinct and unlikely to conflict with unrelated skills.

Suggestions

Add an explicit 'Use when' clause, e.g. 'Use when a Spec Kit command has completed and changes should be committed automatically.'

Expand the action list to mention per-command commit messages and per-event enabling, e.g. 'Auto-commit changes after a Spec Kit command completes, with per-event toggles and custom messages.'

Include a few natural trigger synonyms such as 'git commit', 'auto-commit', and 'spec-kit hook' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names one concrete action — "Auto-commit changes" — in a clear domain (Spec Kit), matching the anchor for naming the domain plus 1-2 concrete actions; it does not list multiple actions that would lift it to a 4.	3 / 5
Completeness	It clearly states what the skill does ("Auto-commit changes after a Spec Kit command completes") but provides no explicit "when to use it" trigger clause; per the rubric, a missing 'Use when...' clause caps completeness at 3.	3 / 5
Trigger Term Quality	It includes natural terms a user might say ("auto-commit", "commit changes", "Spec Kit command"), but coverage is partial and lacks synonyms or file extensions; it is above a 2 because the core phrases are present, below a 4 because common variations are missing.	3 / 5
Distinctiveness Conflict Risk	The Spec Kit hook context and "after a Spec Kit command" scoping give it a clear niche with minimal overlap; it is not a 5 only because the single-action phrasing is not maximally differentiated from a generic git-commit skill.	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-commit/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.