CtrlK
BlogDocsLog inGet started
Tessl Logo

speckit-git-commit

Auto-commit changes after a Spec Kit command completes

57

Quality

66%

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

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 body is concise, well-structured, and provides concrete executable commands plus a ready-to-use config example. Its main weakness is workflow clarity: a destructive/batch auto-commit operation lacks post-commit validation or a feedback loop, capping that dimension at 3.

Suggestions

Add a post-commit verification step (e.g. run 'git status' / confirm the commit was created) and a retry-on-failure loop to satisfy the batch-operation validation requirement.

Show or inline the key logic of auto-commit.sh so the guidance is fully copy-paste executable rather than delegating to an external script.

Clarify how a failed commit is surfaced and recovered (feedback loop) given that 'git add .' silently stages all changes.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding about concepts Claude already knows; sections (Behavior, Execution, Configuration, Graceful Degradation) each earn their place. Every token appears to serve a purpose.

5 / 5

Actionability

Provides concrete executable invocations (auto-commit.sh / auto-commit.ps1 with the <event_name> argument) and a copy-paste-ready YAML config block. It stops short of fully executable logic because the actual commit behavior lives in external scripts not shown here.

4 / 5

Workflow Clarity

The Behavior steps are clearly sequenced (1-6) with pre-flight checks in Graceful Degradation, but this is a batch operation ('git add .' stages all changes) with no post-commit validation/verification or feedback loop, which caps workflow clarity at 3 per the batch-operations guideline.

3 / 5

Progressive Disclosure

This is a short, single-purpose skill (~45 lines) with no bundle files and no need for external references; content is cleanly split into well-labeled sections, satisfying the simple-skill exception for a top score.

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 concise and names a specific action and domain, but it omits an explicit 'Use when...' trigger clause and lacks keyword synonyms, capping several dimensions at the midpoint. It is reasonably distinct thanks to the Spec Kit qualifier.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers, e.g. 'Use when a Spec Kit command finishes and you want changes auto-committed.'

Include synonym keywords such as 'git commit', 'stage changes', or 'checkpoint' so the description matches natural phrasing.

Mention 1-2 more concrete behaviors (e.g. 'stages all changes and writes a configurable commit message') to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('Spec Kit command') and one concrete action ('Auto-commit changes'), but coverage is not comprehensive and only a single action is stated. It is above score 2 because the action is specific rather than generic/minimal.

3 / 5

Completeness

The 'what' is clear ('Auto-commit changes') and a weak 'when' is implied ('after a Spec Kit command completes'), but there is no explicit 'Use when...' trigger clause, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Relevant keywords like 'auto-commit', 'changes', and 'Spec Kit command' appear, but common synonyms (e.g. 'git commit', 'save', 'checkpoint') are missing. It lacks a natural 'Use when...' trigger phrase, keeping it at the midpoint.

3 / 5

Distinctiveness Conflict Risk

The 'Spec Kit command' qualifier gives it a clear niche with minimal conflict risk against generic skills; only minor overlap with broader git-commit skills keeps it just below 5.

4 / 5

Total

13

/

20

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.