speckit-git-commit
Auto-commit changes after a Spec Kit command completes
60
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/speckit-git-commit/SKILL.mdQuality
Discovery
57%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 concise and identifies a clear, narrow use case (auto-committing after Spec Kit commands), which gives it strong distinctiveness. However, it lacks an explicit 'Use when...' clause, provides only a single action without elaboration, and could benefit from more natural trigger terms that users might employ when needing this functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when a Spec Kit command finishes and changes need to be committed to git automatically.'
Include additional trigger terms users might naturally say, such as 'git commit', 'save changes', 'commit after spec', or 'automatic commit'.
Expand the capability description slightly to clarify what the auto-commit involves, e.g., 'Automatically stages and commits changes to git after a Spec Kit command completes, generating a descriptive commit message.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific action ('auto-commit changes') and a domain context ('Spec Kit command'), but doesn't list multiple concrete actions or elaborate on what the auto-commit entails beyond the single action. | 2 / 3 |
Completeness | Answers 'what' (auto-commit changes) and implies 'when' (after a Spec Kit command completes), but lacks an explicit 'Use when...' clause with trigger guidance. The when is embedded but not explicitly called out. | 2 / 3 |
Trigger Term Quality | Includes 'auto-commit' and 'Spec Kit' as relevant keywords, but misses common variations users might say like 'git commit', 'save changes', 'commit after running', or 'automatic commit'. 'Spec Kit' is a specific product term that helps but limits broader discoverability. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'auto-commit' and 'Spec Kit command' creates a very specific niche that is unlikely to conflict with other skills. It's clearly scoped to a particular tool and workflow. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that clearly communicates when and how auto-commit runs, with actionable commands and a ready-to-use configuration example. Its main weakness is the lack of any verification or error-recovery guidance after the git commit step, which is notable for a destructive operation (committing all files via `git add .`). The graceful degradation section partially addresses edge cases but doesn't cover post-commit validation.
Suggestions
Add a brief verification step after the commit (e.g., 'Verify with `git log --oneline -1` that the commit was created as expected') to improve workflow clarity for this potentially destructive `git add .` operation.
Consider noting risks of `git add .` (e.g., committing unintended files) and suggesting a `.gitignore` check or `git status` review as a safeguard.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose—behavior logic, execution commands, configuration example, and edge cases. No unnecessary explanations of what Git is or how hooks work. | 3 / 3 |
Actionability | Provides concrete executable commands for both Bash and PowerShell with the exact script paths and argument format. The YAML configuration example is copy-paste ready with clear key-value semantics. | 3 / 3 |
Workflow Clarity | The behavior section clearly sequences the decision logic (steps 1-6), and execution is straightforward. However, there are no validation or verification steps—no way to confirm the commit succeeded, check what was committed, or recover from errors like merge conflicts or dirty index states. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized into clear sections (Behavior, Execution, Configuration, Graceful Degradation) with no need for external references. The structure is easy to navigate. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%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
3ce3191
- Reviewed
Table of Contents
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.