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'.
54
44%
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 does a good job of stating what the skill does (generate conventional commit messages) and when to use it, with explicit trigger terms. However, the description appears truncated ('especially a...'), reducing specificity, and some trigger terms like 'branch' and 'version control' are overly broad, which could cause conflicts with other git-related skills.
Suggestions
Fix the truncated text ('especially a...') to complete the full description of capabilities.
Narrow the trigger terms to focus more specifically on commit message generation rather than broad git operations—consider removing 'branch' and 'version control' or qualifying them (e.g., 'commit message', 'conventional commits', 'git commit').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (conventional commit messages) and some actions (analyzes code changes, suggests a commit message), but the description is truncated ('especially a...') and doesn't list multiple concrete actions comprehensively. | 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'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'commit', 'branch', 'git', 'commit messages', 'version control'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The trigger terms 'branch' and 'git' are quite broad and could overlap with other git-related skills (e.g., branching strategies, git workflow skills). The core focus on conventional commit messages is distinct, but the broad triggers like 'version control' increase conflict risk. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
7%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 boilerplate and filler content with no actionable implementation details. It explains what conventional commits are and describes the concept of generating commit messages at a high level, but provides zero concrete guidance—no git commands, no code for analyzing diffs, no prompt templates, no commit type selection logic. Multiple sections ('Prerequisites', 'Instructions', 'Output', 'Error Handling', 'Resources') appear to be generic template placeholders with no task-specific content.
Suggestions
Replace the abstract 'How It Works' section with concrete executable steps: e.g., run `git diff --staged`, analyze the output, select the appropriate conventional commit type prefix, and format the message.
Add a concrete mapping or decision logic for selecting commit types (feat/fix/refactor/chore/docs/style/test/ci) based on the nature of changes detected in the diff.
Remove all generic boilerplate sections ('Prerequisites', 'Instructions', 'Output', 'Error Handling', 'Resources') that contain no task-specific information and waste tokens.
Include at least one complete worked example showing actual diff input and the resulting commit message with reasoning for the type selection.
| 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 no actionable information. Claude already knows what conventional commits are and doesn't need to be told 'It saves you time and ensures consistency.' | 1 / 3 |
Actionability | No executable code, no concrete commands (not even `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 changes or construct the message. Everything describes rather than instructs. | 1 / 3 |
Workflow Clarity | The 'How It Works' section describes an abstract 3-step process ('Analyze Changes', 'Generate Suggestion', 'Present to User') with no concrete commands, no validation steps, and no error recovery. The 'Instructions' section is completely generic boilerplate with no task-specific guidance. | 1 / 3 |
Progressive Disclosure | The content has section headers providing some structure, but it's a monolithic file with no references to external resources. Much of the content is filler that inflates the document unnecessarily, though the sections themselves are at least organized logically. | 2 / 3 |
Total | 5 / 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
c8a915c
- 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.