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.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill commit-message-formatterActivation
7%This description is severely lacking in substance - it's essentially just a title with metadata rather than a functional description. It provides no information about what the skill actually does, what actions it performs, or when Claude should select it. The repeated trigger term and boilerplate category information add no value for skill selection.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Formats commit messages following conventional commit standards, generates descriptive messages from git diffs, validates message structure'
Add a 'Use when...' clause with natural trigger terms like 'commit', 'git message', 'staged changes', 'conventional commits', 'commit format'
Remove the redundant 'Triggers on' line that just repeats the skill name, and replace with meaningful trigger conditions
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Commit Message Formatter') without describing any concrete actions. There are no verbs explaining what it 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 explicit use-case guidance). The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'commit message formatter' repeated twice, which is the skill name itself rather than natural user language. Missing common variations like 'commit', 'git message', 'write commit', 'format commit', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Commit Message Formatter' is somewhat specific to git/version control domain, which provides some distinctiveness. However, without concrete actions described, it could overlap with other git-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%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. A proper skill would include the actual commit message format (e.g., Conventional Commits), concrete examples of good and bad messages, and possibly validation rules.
Suggestions
Add the actual commit message format specification (e.g., 'type(scope): subject' with allowed types like feat, fix, docs, etc.)
Include 2-3 concrete examples showing input changes and the expected formatted commit message output
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable formatting rules
Add validation criteria for what makes a commit message valid or invalid
| 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, no examples of good/bad messages, no executable code or templates. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined. For a commit message formatter, there should be clear steps or a format specification (e.g., type(scope): description), but none exists. | 1 / 3 |
Progressive Disclosure | The content is organized into sections, but they contain no useful information. There are no references to detailed materials because there's no substance to disclose progressively. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.