generating-conventional-commits
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-conventional-commitsExecute 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'.
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
7%This skill content is largely boilerplate with minimal actionable guidance. It explains concepts Claude already understands, provides no executable code or commands, and includes generic placeholder sections that add no value. The skill would benefit from being reduced to a concise, code-focused document showing exactly how to analyze git diffs and generate conventional commit messages.
Suggestions
Replace the abstract 'How It Works' section with actual executable code showing how to get staged changes (e.g., `git diff --cached`) and format them into conventional commit messages
Remove all generic boilerplate sections (Prerequisites, Instructions, Output, Error Handling, Resources) that provide no skill-specific value
Add concrete examples with actual input (sample diff output) and expected output (complete commit message with body and footer)
Include the conventional commits specification format (type, scope, description, body, footer) as a concrete reference rather than just mentioning it exists
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with redundant explanations. The overview is repeated, explains obvious concepts like what conventional commits are, and includes generic boilerplate sections (Prerequisites, Instructions, Output, Error Handling) that add no value and describe things Claude already knows. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance. Examples show conceptual outputs but no actual implementation. Instructions like 'Invoke this skill when trigger conditions are met' are completely vague and non-actionable. | 1 / 3 |
Workflow Clarity | The 'How It Works' section describes abstract steps without any concrete commands or validation. No actual Git commands, no way to stage changes, no verification steps. The workflow is descriptive rather than instructive. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but it's a monolithic document with no references to external files. The structure exists but contains too much filler content that should either be removed or properly organized into separate reference materials. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
82%This description effectively communicates its core purpose and includes explicit trigger guidance, which is a strength. However, the description appears truncated ('especially a...') and some trigger terms like 'branch' are overly broad for a commit message skill, creating potential conflict with other git-related skills.
Suggestions
Narrow trigger terms to be more specific to commit messages - remove 'branch' and add terms like 'staged changes', 'git diff', 'commit message'
Complete the truncated description and add more specific actions like 'analyzes staged changes', 'follows conventional commit format with type/scope/description'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (commit messages, conventional commits) and describes the core action (analyzes code changes, suggests commit message), but doesn't list multiple concrete actions beyond message generation. | 2 / 3 |
Completeness | Clearly answers both what (generates conventional commit messages by analyzing code changes) and when (explicit 'Use when managing version control' and 'Trigger with phrases like...' clauses). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'commit', 'branch', 'git', 'commit messages', 'version control'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | While commit message generation is specific, the broad triggers like 'branch' and general 'git' could overlap with other git-related skills (e.g., branch management, merge conflict resolution). | 2 / 3 |
Total | 10 / 12 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.