generating-smart-commits
Execute use when generating conventional commit messages from staged git changes. Trigger with phrases like "create commit message", "generate smart commit", "/commit-smart", or "/gc". Automatically analyzes changes to determine commit type (feat, fix, docs), identifies breaking changes, and formats according to conventional commit standards.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-smart-commits74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 is a strong skill description that excels across all dimensions. It provides specific actions (analyzing changes, determining commit types, identifying breaking changes), includes natural trigger phrases users would actually say, explicitly states when to use it, and occupies a clear niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'analyzes changes to determine commit type (feat, fix, docs)', 'identifies breaking changes', and 'formats according to conventional commit standards'. | 3 / 3 |
Completeness | Clearly answers both what (generating conventional commit messages, analyzing changes, determining commit type, identifying breaking changes) AND when ('Trigger with phrases like...' provides explicit trigger guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'create commit message', 'generate smart commit', '/commit-smart', '/gc', plus domain terms like 'conventional commit', 'staged git changes'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on conventional commit message generation from staged git changes, with distinct triggers like '/commit-smart' and '/gc' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable framework for generating conventional commit messages with clear steps and good output examples. However, it lacks executable commands (no `git diff --staged` example), contains redundant/empty sections, and explains prerequisites Claude already understands. The error handling is helpful but disconnected from the main workflow.
Suggestions
Add executable git commands for analyzing staged changes, e.g., `git diff --staged --stat` and `git diff --staged` examples
Remove empty placeholder sections (Overview, Examples at the end) and the redundant opening sentence
Integrate validation into the workflow: after step 5, add explicit format validation before presenting to user
Remove or condense Prerequisites section - Claude knows what git init and git add do
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary padding like 'This skill provides automated assistance for git commit smart tasks' and redundant sections (Overview at the end repeats nothing useful). Prerequisites section explains things Claude would know, but the core instructions are reasonably tight. | 2 / 3 |
Actionability | Provides clear steps and good output format examples, but lacks executable code. No actual git commands for analyzing diff (e.g., `git diff --staged`), no script or command to run. The instructions describe what to do conceptually rather than providing copy-paste commands. | 2 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced with a review checkpoint before committing. However, there's no explicit validation step for the generated message format, and the error handling section is separate from the workflow rather than integrated as checkpoints. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the Overview and Examples sections at the end are empty placeholders that add no value. References to external resources are present but the internal structure could be tighter. | 2 / 3 |
Total | 8 / 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 — 13 / 16 Passed
Validation for skill structure
| 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 | |
- 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.