speckit-git-commit

Disabled — commits are performed manually by the user, never by Spec Kit

Quality

60%

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 ./.agents/skills/speckit-git-commit/SKILL.md

Quality

Content

78%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.

This disabled guard-rail skill is lean, concrete, and well-structured: it gives exact no-op steps, names the scripts and config to avoid, and provides a verified re-enabling path. It is a strong, token-efficient instruction-only skill.

Dimension	Reasoning	Score
Conciseness	The body is focused and assumes Claude's competence, citing project-specific rationale (commit-message format requiring Trello-aware data) rather than generic git concepts; only minor repeated emphasis ('never commit') could be trimmed.	4 / 5
Actionability	Concrete, executable guidance is given throughout—numbered no-op steps naming exact paths (.specify/extensions/git/git-config.yml) and scripts to avoid (auto-commit.sh / auto-commit.ps1), plus a concrete re-enabling sequence; minor gaps include no exact output line format or report mechanism.	4 / 5
Workflow Clarity	The no-op behavior is an unambiguous numbered sequence and the re-enabling flow includes a verification checkpoint ('Confirm the commit message template matches task.md's commit style before enabling'); the main flow has nothing destructive to validate, leaving only minor checkpoint gaps.	4 / 5
Progressive Disclosure	At under 50 lines with no need for external references, the well-organized sections (Behavior, Rationale, Execution, Re-enabling) satisfy the simple-skill exception for a top progressive-disclosure score.	5 / 5
	Total	17 / 20 Passed

Description

41%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 clearly conveys the skill is a disabled no-op around Spec Kit commits, but it lacks any explicit trigger guidance and relies on a negation rather than concrete actions. It is distinctive but incomplete for discovery.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when Spec Kit would otherwise auto-commit; this skill is a no-op that defers all commits to the user.'

Replace the pure negation with a concrete behavioral statement such as 'Returns immediately without staging or committing; the user commits manually.'

Surface natural trigger terms like 'auto-commit', 'git commit', and 'spec-kit commit hook' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("commits") but the only action framing is a negation ("performed manually by the user, never by Spec Kit"), with no affirmative list of concrete actions the skill performs.	2 / 5
Completeness	There is a clear "what" (the skill is disabled; commits are manual, never by Spec Kit) but the "when" is only weakly implied and there is no explicit "Use when..." trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	"commits" is a natural keyword but no trigger phrasing or synonyms (e.g. "auto-commit", "git commit") appear, and there is no "Use when..." clause to surface the natural phrases a user would say.	2 / 5
Distinctiveness Conflict Risk	The Spec Kit + commit pairing is a clear niche with distinct triggers, with only minor overlap risk against generic git-commit skills.	4 / 5
	Total	11 / 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: g14wx/staffSync
Path: .agents/skills/speckit-git-commit/SKILL.md
Commit: 682bfbc

Reviewed: 1 day 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.