commit
Stage and commit changes following conventional commits. Auto-bumps package versions before committing.
76
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
42%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 specific capabilities (staging, committing with conventional format, auto-bumping versions) but critically lacks explicit trigger guidance. Without a 'Use when...' clause, Claude may struggle to select this skill appropriately from a large skill library. The trigger terms are adequate but could include more natural user language variations.
Suggestions
Add a 'Use when...' clause with trigger terms like 'commit message', 'git commit', 'version bump', 'conventional commit', or 'prepare release'
Include common file/format references users might mention: 'package.json', 'semver', 'changelog'
Specify the scope more clearly to distinguish from general git skills, e.g., 'for Node.js/npm projects' if applicable
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Stage and commit changes', 'following conventional commits', and 'Auto-bumps package versions'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly describes WHAT the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for WHEN Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains relevant keywords like 'commit', 'stage', 'conventional commits', and 'package versions', but missing common variations users might say like 'git', 'version bump', 'semver', or 'changelog'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'conventional commits' and 'auto-bumps package versions' provides some distinctiveness, but 'stage and commit changes' is generic enough to potentially overlap with other git-related skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates best practices: it's concise yet complete, provides executable commands at every step, includes validation checkpoints (typecheck, git status verification), and has clear warnings about dangerous operations (amending commits, --no-verify). The workflow is well-sequenced with appropriate feedback loops for error recovery.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining concepts Claude already knows. Each section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable commands throughout (git commands, pnpm scripts, HEREDOC syntax for commits). The conventional commit format is clearly specified with concrete examples and rules. | 3 / 3 |
Workflow Clarity | Clear 7-step sequence with explicit validation checkpoints (typecheck in Step 4, verify in Step 7). Includes feedback loops ('If typecheck fails, fix the errors') and explicit warnings about what NOT to do. | 3 / 3 |
Progressive Disclosure | Well-organized with clear section headers for each step. Content is appropriately sized for a single SKILL.md file (~80 lines) without needing external references. Easy to navigate and scan. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.