CtrlK
BlogDocsLog inGet started
Tessl Logo

speckit-git-commit

Auto-commit changes after a Spec Kit command completes

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/speckit-git-commit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is well-structured and highly actionable with concrete script paths, a complete config example, and explicit graceful-degradation guards, so actionability, workflow clarity, and progressive disclosure all score at the top anchor. The only weakness is mild redundancy between the Behavior and Execution sections, which keeps conciseness at the middle anchor.

Suggestions

Tighten conciseness by trimming the Behavior section so it does not restate the script's internal logic that Execution already delegates to auto-commit.sh / auto-commit.ps1.

Consider collapsing the duplicated "determine the event name" instruction that appears in both the Behavior steps and the Execution paragraph into a single statement.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanations of git or Spec Kit), but the 6-step Behavior section re-describes the script's internals that Execution then hands off to a bundled script, a mild tightening opportunity that matches the score-2 anchor of mostly efficient but could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands for both Bash and PowerShell with explicit script paths, a clearly explained <event_name> placeholder with concrete event examples, and a complete YAML config sample, matching the score-3 anchor of fully executable code and specific examples.

3 / 3

Workflow Clarity

The single task is unambiguous with a clear numbered sequence and explicit guard/skip conditions in the Graceful Degradation section (no git, no config, no changes), which serve as the validation checkpoints for this potentially destructive operation, matching the score-3 anchor for simple skills with clear sequencing and explicit validation.

3 / 3

Progressive Disclosure

This under-50-line single-task skill has no bundle files and no need for external references, and its body is well-organized into four clear sections (Behavior, Execution, Configuration, Graceful Degradation), meeting the score-3 carve-out for simple skills with well-organized sections.

3 / 3

Total

11

/

12

Passed

Description

50%

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 names a concrete action and a specific domain, but it lacks an explicit "Use when..." trigger clause and multiple concrete actions, so every dimension lands at the middle anchor. Adding trigger guidance and a second concrete action would raise specificity, completeness, and distinctiveness.

Suggestions

Add an explicit "Use when..." clause naming the natural triggers, e.g. "Use when a Spec Kit command (specify, plan, implement) completes and you want changes auto-committed via git."

List at least one more concrete action or variation to lift specificity, such as "Auto-commit staged changes after Spec Kit commands (specify/plan/implement), using per-command commit messages."

Include common trigger terms users would say ("git commit", "commit my changes", "after I run spec-kit") to improve trigger-term coverage and reduce overlap with generic commit skills.

DimensionReasoningScore

Specificity

Names a concrete action and domain ("Auto-commit changes" after a "Spec Kit command") but does not list multiple specific concrete actions, matching the score-2 anchor that names domain and some actions without being comprehensive.

2 / 3

Completeness

Clearly answers "what" (auto-commits changes) but the "when" is only implied via "after a Spec Kit command completes" with no explicit trigger guidance; per the judging guidelines a missing "Use when..." clause caps completeness at 2.

2 / 3

Trigger Term Quality

Includes some natural keywords a user might say ("Auto-commit", "commit", "changes") but lacks a "Use when..." clause and misses common variations like "git commit" or "save my changes", matching the score-2 anchor of some relevant keywords with missing variations.

2 / 3

Distinctiveness Conflict Risk

The "Spec Kit command" scoping gives it a niche, but the "auto-commit changes" action could overlap with general git-commit skills and there is no explicit trigger clause to prevent conflicts, matching the score-2 anchor of somewhat specific but still potentially overlapping.

2 / 3

Total

8

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
unoplatform/uno
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.