commit-message

Generate a clean, conventional commit message from a description of your changes.

Quality

75%

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 ./skills/gemma/commit-message/SKILL.md

Quality

Content

100%Weight 40%Scale 1-3

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

The body is a lean, fully actionable instruction set that gives Claude an exact tool contract and illustrative examples with no wasted tokens, scoring top marks across all content dimensions.

Dimension	Reasoning	Score
Conciseness	The body is lean — a one-line intro, four short illustrative examples, and a tight parameter block — with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	It specifies exact `run_js` parameters with a complete JSON data contract (type enum, scope, message constraints, body), giving copy-paste-ready executable guidance.	3 / 3
Workflow Clarity	As a simple single-purpose skill the single action (call `run_js` with the data) is unambiguous and well-illustrated by examples, satisfying the simple-skill allowance for a top score.	3 / 3
Progressive Disclosure	Under 50 lines with clear Examples and Instructions sections and no nested or poorly-signaled references; the HTML bundle assets are implementation files used by tooling rather than markdown docs needing navigation.	3 / 3
	Total	12 / 12 Passed

Description

50%Weight 40%Scale 1-3

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 concretely states the skill's single capability in third person but lacks an explicit 'Use when' trigger and broader natural keyword coverage, leaving every dimension at the mid level.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks for a commit message or is about to commit staged changes.'

Broaden trigger terms to include natural variations like 'git commit', 'write a commit', or 'commit my changes'.

Optionally name a second concrete action (e.g. 'format and suggest conventional commit messages') to lift specificity toward a 3.

Dimension	Reasoning	Score
Specificity	Names the commit-message domain and a concrete action ('Generate a clean, conventional commit message') but offers only a single action rather than the multiple specific concrete actions required for a 3.	2 / 3
Completeness	Clearly states what the skill does but provides no 'Use when...' trigger for when to invoke it; the rubric guideline caps completeness at 2 when explicit trigger guidance is missing.	2 / 3
Trigger Term Quality	Includes the natural term 'commit message' but misses common variations users might say ('git commit', 'write a commit', 'committing'), so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	The 'commit message' niche is fairly distinct and unlikely to broadly conflict, but the single-action phrasing without a richer explicit trigger keeps it from the clear-niche-with-distinct-triggers level 3.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: mergisi/awesome-openclaw-agents
Path: skills/gemma/commit-message/SKILL.md
Commit: 05820c5

Reviewed: 8 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.