git-commit

Generate well-formatted git commit messages following conventional commit standards

Quality

57%

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

Quality

Content

57%

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

The content is well-structured and concise enough, with executable git commands, but it lacks a concrete worked commit-message example and a verification step before committing. These gaps keep the actionable and workflow dimensions at mid-tier.

Suggestions

Add at least one worked example showing a staged diff and the resulting full commit message (type(scope): subject plus body).

Insert an explicit validation step before committing, e.g. confirm staged changes exist and verify the message conforms to the format before running git commit.

Trim the Conventional Commit types list and basic subject-line rules to only non-obvious guidance, since Claude already knows these conventions.

Dimension	Reasoning	Score
Conciseness	The body restates Conventional Commit types and basic subject-line rules (imperative mood, no period, 50 chars) that Claude already knows, so it is mostly efficient but padded with familiar material.	2 / 3
Actionability	It gives concrete commands (git diff --staged, git commit -m) and a format template, but provides no worked example commit message showing input to output, leaving guidance incomplete.	2 / 3
Workflow Clarity	Steps are sequenced with a user-confirmation checkpoint, but there is no validation/verification step before committing, which the guidelines cap at 2 for destructive operations.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no bundle files and well-organized sections (Format, Types, Guidelines, Workflow), so progressive disclosure scores 3 per the simple-skill note.	3 / 3
	Total	9 / 12 Passed

Description

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 specific and occupies a clear niche, but it lacks an explicit "Use when..." trigger clause and broader trigger-term coverage, leaving it solidly mid-tier. Adding a trigger clause would lift the completeness and trigger dimensions.

Suggestions

Append a 'Use when...' trigger clause, e.g. 'Use when the user asks for help writing commit messages or reviewing staged changes.'

Broaden trigger terms to include 'commit', 'commit message', 'staged changes', and 'git diff' for better natural-keyword coverage.

Optionally add a second concrete action (e.g. 'review staged changes') to raise specificity to anchor 3.

Dimension	Reasoning	Score
Specificity	"Generate well-formatted git commit messages following conventional commit standards" names one concrete action and the domain, but does not list multiple specific actions, matching anchor 2 rather than the multi-action anchor 3.	2 / 3
Completeness	It states what the skill does but includes no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	"git commit messages" is a natural keyword, but common variations like "commit", "staged changes", or "diff" are absent, so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	The git commit message niche is distinct and unlikely to trigger for unrelated skills, matching the clear-niche anchor 3.	3 / 3
	Total	9 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: ThinkInAIXYZ/deepchat
Path: resources/skills/git-commit/SKILL.md
Commit: b8dbc89

Reviewed: about 7 hours 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.