commit

Create well-formatted commits with conventional commit messages and emoji

Quality

55%

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

Quality

Content

56%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 skill delivers concrete, well-sequenced commit guidance with validation checkpoints, but it is weighed down by a very large inlined emoji catalog that hurts token efficiency and structure. Moving that catalog to a reference file would improve both conciseness and progressive disclosure.

Suggestions

Move the emoji-to-type catalog into a separate references file (e.g. references/emoji-types.md) and link to it, keeping only the most common mappings inline.

Trim redundant emoji entries (e.g. multiple emojis mapping to 'feat'/'fix'/'chore') to the essential set, or mark the extended list as optional.

Add an explicit fix-and-retry loop around the pre-commit checks rather than only offering to proceed anyway.

Dimension	Reasoning	Score
Conciseness	The 60+ entry emoji-to-type catalog is a large padded section with many redundant mappings (multiple emojis per type, obscure entries like easter eggs), inflating tokens well beyond what the core workflow needs.	2 / 5
Actionability	Concrete commands appear throughout ('git status', 'git add', 'git diff', 'pnpm lint') with concrete commit-message examples and a branch-naming pattern, leaving only minor gaps such as the literal commit command format.	4 / 5
Workflow Clarity	The 8-step sequence is clearly ordered with a validation checkpoint (pre-commit lint/build with a proceed-or-fix prompt) and a branch-safety prompt, so the destructive/batch cap does not apply; minor validation gaps remain.	4 / 5
Progressive Disclosure	Headers organize the body well, but the large emoji reference table is inlined rather than split into a separate reference file, and no bundle references exist to offload it.	3 / 5
	Total	13 / 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 states clearly what the skill does but omits any explicit trigger guidance for when to use it. Specificity and trigger-term coverage are adequate but not comprehensive.

Suggestions

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

Include natural trigger phrases users actually say such as 'git commit', 'commit my changes', or 'write a commit message'.

Mention the splitting/staging behavior to broaden specificity beyond message formatting.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple concrete actions ('Create well-formatted commits with conventional commit messages and emoji'), but coverage is not comprehensive — no mention of staging, splitting, or branch handling.	3 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Relevant keywords ('commits', 'commit messages', 'conventional commit') appear, but common natural variations users say ('git commit', 'write a commit message', 'commit my changes') are missing.	3 / 5
Distinctiveness Conflict Risk	The 'conventional commit messages and emoji' framing carves out a clear niche distinct from generic git skills, with only minor overlap risk.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: NeoLabHQ/context-engineering-kit
Path: plugins/git/skills/commit/SKILL.md
Commit: 8539779

Reviewed: 4 days 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.