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.
34
3%
Does it follow best practices?
Impact
86%
0.91xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/commit-message-formatter/SKILL.mdQuality
Discovery
7%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 extremely thin—it essentially restates the skill name without explaining what the skill does, when to use it, or providing useful trigger terms. It reads more like an auto-generated stub than a functional description, offering almost no information for Claude to make an informed skill selection.
Suggestions
Add concrete actions the skill performs, e.g., 'Formats commit messages following conventional commit standards, generates descriptive messages from git diffs, enforces prefix conventions like feat/fix/chore.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to write, format, or review commit messages, or mentions git commits, staged changes, or conventional commits.'
Remove the duplicated trigger term and expand with natural variations users would say, such as 'commit message', 'git message', 'conventional commit', 'write a commit'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description does not list any concrete actions. It says 'Commit Message Formatter' but never explains what it actually does—no mention of formatting rules, generating messages, analyzing diffs, or any specific capabilities. | 1 / 3 |
Completeness | The 'what' is essentially absent beyond the name, and the 'when' is only a redundant trigger phrase with no meaningful guidance on when Claude should select this skill. There is no 'Use when...' clause or equivalent. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'commit message formatter' repeated twice. It misses natural user phrases like 'commit message', 'git commit', 'write a commit', 'staged changes', or 'git log format'. | 1 / 3 |
Distinctiveness Conflict Risk | The name 'Commit Message Formatter' is somewhat specific to a niche domain, which reduces conflict risk slightly, but the lack of concrete detail means it could overlap with any general git or DevOps skill. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%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 substantive content. It describes what a commit message formatter skill would do without actually providing any formatting rules, examples, conventions (like Conventional Commits), or actionable guidance. It fails on every dimension because it contains zero instructional content.
Suggestions
Add the actual commit message format specification (e.g., Conventional Commits: `type(scope): description`) with concrete examples of input changes mapped to properly formatted commit messages.
Include at least 2-3 before/after examples showing bad commit messages transformed into good ones, similar to: Input: 'fixed bug' → Output: 'fix(auth): resolve token expiration check in middleware'.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') and replace with actionable content: the format rules, allowed types/scopes, and validation criteria.
Add a quick-reference section with the commit message template and constraints (e.g., subject line max length, body formatting rules, footer conventions for breaking changes).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, commands, or commit message formatting rules. Every section describes rather than instructs. | 1 / 3 |
Actionability | There is zero concrete guidance—no commit message format specification, no examples of good/bad commit messages, no executable code or commands. Phrases like 'Provides step-by-step guidance' promise action but deliver none. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints for formatting commit messages. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-descriptions with no meaningful structure. There are no references to detailed files, no examples section, and no navigable hierarchy—just repeated vague descriptions of the same concept. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%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 | |
- Commit
1531b64
- Reviewed
Table of Contents
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.