generating-conventional-commits
Execute generates conventional commit messages using AI. It analyzes code changes and suggests a commit message adhering to the conventional commits specification. Use this skill when you need help writing clear, standardized commit messages, especially a... Use when managing version control. Trigger with phrases like 'commit', 'branch', or 'git'.
51
41%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/packages/devops-automation-pack/skills/generating-conventional-commits/SKILL.mdQuality
Discovery
82%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 effectively communicates its core purpose (generating conventional commit messages) and includes explicit trigger guidance, which is a strength. However, the description appears truncated ('especially a...'), reducing specificity, and the trigger terms ('branch', 'version control') are broader than the skill's actual capability, creating potential conflict risk with other git-related skills.
Suggestions
Fix the truncated text ('especially a...') to complete the description and add more specific actions like 'formats messages with type prefixes (feat, fix, chore), scopes, and breaking change indicators'.
Narrow trigger terms to focus on commit-specific phrases rather than broad git terms—e.g., replace 'branch' and 'version control' with 'commit message', 'staged changes', 'git diff' to reduce conflict risk with other git skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (conventional commit messages) and some actions (analyzes code changes, suggests a commit message), but doesn't list multiple concrete actions beyond that. The description is cut off ('especially a...') which limits comprehensiveness. | 2 / 3 |
Completeness | Clearly answers both 'what' (generates conventional commit messages by analyzing code changes) and 'when' (explicit 'Use when managing version control. Trigger with phrases like commit, branch, or git'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'commit', 'branch', 'git', 'commit messages', 'version control', 'conventional commits'. Good coverage of terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The mention of 'branch' and general 'version control' could cause overlap with other git-related skills (e.g., branching strategies, merge conflict resolution). The core focus on conventional commit messages is distinct, but the trigger terms are broader than the actual capability. | 2 / 3 |
Total | 10 / 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 almost entirely generic boilerplate with no actionable, task-specific content. It lacks executable code (e.g., git commands to inspect staged changes), concrete implementation details, and any real workflow guidance. Multiple sections ('Prerequisites', 'Instructions', 'Output', 'Error Handling', 'Resources') appear to be template placeholders that were never filled in with actual content.
Suggestions
Replace the abstract 'How It Works' section with a concrete workflow: e.g., run `git diff --staged`, analyze the diff, select the appropriate conventional commit type, and format the message with specific rules for subject line length, scope, and body.
Add executable examples showing the actual git commands used and the exact format of conventional commit messages, including the full type list (feat, fix, docs, style, refactor, perf, test, build, ci, chore) with brief descriptions.
Remove all generic boilerplate sections (Prerequisites, Instructions, Output, Error Handling, Resources) that contain no task-specific information.
Include concrete rules for conventional commit formatting: subject line max length, when to include scope, when to add a body, breaking change notation (BREAKING CHANGE footer or ! after type).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding. Sections like 'Overview', 'When to Use This Skill', 'Best Practices', 'Integration', 'Prerequisites', 'Instructions', 'Output', 'Error Handling', and 'Resources' are all filler that explain obvious concepts or provide vague platitudes. Claude doesn't need to be told what a commit message is or that it should 'review the generated output'. | 1 / 3 |
Actionability | No executable code, no concrete commands (e.g., `git diff --staged`), no actual implementation details. The 'Instructions' section is entirely generic ('Invoke this skill when the trigger conditions are met'). The examples show desired outputs but not how to actually analyze staged changes or construct the message. | 1 / 3 |
Workflow Clarity | The 'How It Works' section describes an abstract 3-step process ('Analyze Changes', 'Generate Suggestion', 'Present to User') without any concrete commands, validation steps, or error recovery. The 'Instructions' section is completely generic boilerplate with no task-specific workflow. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no bundle files and no meaningful references. All sections are inline despite most being unnecessary filler. The 'Resources' section lists 'Project documentation' and 'Related skills and commands' without any actual links or paths. | 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
3a2d27d
- 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.