git-commit

Create well-structured git commits with conventional commit messages, proper staging, and commit best practices.

Quality

58%

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 ./apps/desktop/bundled-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 appropriately concise for a simple single-purpose skill, but it loses points for restating known concepts, omitting a concrete `git commit` command and worked message example, and leaving its verification step vague without an error-recovery loop.

Suggestions

Add a worked example: show an input change and the resulting `git commit -m "feat(auth): ..."` command with a full conventional-commit message body.

Make the verification step explicit with a command (e.g. `git log -1` or `git status`) and add a brief error-recovery note for when staging or committing fails.

Trim the conventional-commit type definitions and generic best-practice reminders that Claude already knows, keeping only project-specific conventions.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the conventional-commit type list (feat/fix/docs/etc.) and the generic 'Best Practices' reminders restate concepts Claude already knows, so it is 'mostly efficient but includes some unnecessary explanation' rather than every token earning its place.	2 / 3
Actionability	It gives real executable commands (`git status`, `git diff`) and a message format template, but never shows the actual `git commit` command or a worked example commit message — the 'Examples' are trigger phrases, not outputs — so guidance is concrete but incomplete with missing key details.	2 / 3
Workflow Clarity	The 5-step sequence is clear and includes a verify step, but step 5 ('Verify commit was successful') is vague with no specific command and no error-recovery feedback loop, leaving checkpoints present but implicit rather than explicit.	2 / 3
Progressive Disclosure	The skill is under 50 lines, needs no external references (none exist in references/scripts/assets), and is organized into clear sections (Format, Types, Workflow, Best Practices, Examples), which per the simple-skills note earns a 3 on well-organized sections alone.	3 / 3
	Total	9 / 12 Passed

Description

60%

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 action-oriented about creating git commits, but it omits any explicit 'Use when' trigger guidance and lacks the breadth of natural trigger-term variations, leaving completeness and trigger quality at the mid level.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user asks to commit changes, write a commit message, or stage and commit files.'

Broaden trigger terms to include natural variations users say: 'commit my changes', 'write a commit message', 'stage files', 'make a commit'.

Sharpen distinctiveness by naming the conventional-commit focus explicitly in the trigger so it does not overlap with other git workflow skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "Create well-structured git commits", "conventional commit messages", and "proper staging" — matching the score-3 anchor for naming several specific actions rather than vague language.	3 / 3
Completeness	It clearly states what the skill does but has no "Use when..." clause or equivalent explicit trigger for when to invoke it, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant natural terms ("git commits", "commit messages", "staging") but misses common variations users actually say like "commit my changes", "write a commit message", or "stage files", so it lands at 'some relevant keywords but missing common variations' rather than broad coverage.	2 / 3
Distinctiveness Conflict Risk	Git commits are a recognizable niche, but without explicit triggers and with staging/committing overlapping other plausible git workflow skills, it is only 'somewhat specific' and could still overlap, not a clear conflict-free niche.	2 / 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: accomplish-ai/coworker
Path: apps/desktop/bundled-skills/git-commit/SKILL.md
Commit: 2cf74d0

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.