commit-message-formatter

Commit Message Formatter - Auto-activating skill for DevOps Basics. Triggers on: commit message formatter, commit message formatter Part of the DevOps Basics skill category.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill commit-message-formatter

What are skills?

0.91x

Quality

Does it follow best practices?

Impact

86%

0.91x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/commit-message-formatter/SKILL.md

SKILL.md

Review

Evals

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is severely lacking in substance - it reads more like a metadata stub than a functional skill description. It provides no information about what the skill actually does, contains no natural trigger terms users would say, and lacks any guidance on when Claude should select this skill. The description would be nearly useless for skill selection among multiple options.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Generates well-formatted commit messages following conventional commit standards, analyzes git diffs to suggest descriptive messages'

Add a 'Use when...' clause with natural trigger terms like 'commit', 'git message', 'staged changes', 'write commit', 'conventional commits'

Remove the redundant trigger term and replace with varied natural language users would actually say when needing this skill

Dimension	Reasoning	Score
Specificity	The description only names the skill ('Commit Message Formatter') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of formatting, generating, analyzing, or any specific capabilities.	1 / 3
Completeness	The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no 'Use when...' clause or equivalent guidance). It only provides metadata about categorization.	1 / 3
Trigger Term Quality	The only trigger terms listed are 'commit message formatter' repeated twice, which is redundant and unlikely to match natural user language. Users would more naturally say 'write a commit message', 'git commit', 'help with commits', etc.	1 / 3
Distinctiveness Conflict Risk	The name 'Commit Message Formatter' is somewhat specific to a niche (git commits), but without describing actual capabilities, it could overlap with other git-related skills. The lack of detail makes conflict assessment difficult.	2 / 3
	Total	5 / 12 Passed

Implementation

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

This skill is essentially a placeholder with no actionable content. It describes what a commit message formatter skill would do without actually providing any formatting rules, examples, or guidance. The content fails to teach Claude anything about commit message conventions (like Conventional Commits), provides no examples of good vs bad messages, and offers no concrete templates.

Suggestions

Add concrete commit message format specification (e.g., Conventional Commits: type(scope): description)

Include 2-3 input/output examples showing raw change descriptions transformed into properly formatted commit messages

Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual formatting rules

Add validation criteria for what makes a commit message well-formatted (character limits, required components, etc.)

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing specific about commit message formatting. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need.	1 / 3
Actionability	No concrete guidance whatsoever - no commit message format examples, no templates, no actual formatting rules. The content describes what the skill does abstractly rather than providing executable instructions.	1 / 3
Workflow Clarity	No workflow is defined. There are no steps for how to format a commit message, no examples of input/output, and no validation criteria for what makes a good commit message.	1 / 3
Progressive Disclosure	The content is organized into sections with clear headers, but there's no actual content to disclose. No references to additional resources or examples that would provide depth.	2 / 3
	Total	5 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

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