commit
Stage and commit changes following conventional commits. Auto-bumps package versions before committing.
82
76%
Does it follow best practices?
Impact
90%
1.11xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/commit/SKILL.mdQuality
Discovery
67%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 is concise and specific about its capabilities, clearly communicating the dual function of conventional commit creation and automatic version bumping. Its main weakness is the absence of an explicit 'Use when...' clause, which limits Claude's ability to know exactly when to select this skill. Adding natural trigger terms and explicit usage guidance would strengthen it significantly.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks to commit changes, write a commit message, or bump a version.'
Include additional natural trigger terms like 'git', 'commit message', 'version bump', 'semver', or 'release' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'stage and commit changes', 'following conventional commits', and 'auto-bumps package versions before committing'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (stage/commit with conventional commits, auto-bump versions), but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'commit', 'stage', 'conventional commits', and 'package versions', but misses common user variations like 'git', 'commit message', 'version bump', 'semver', or 'changelog'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of conventional commits and auto-bumping package versions creates a clear, distinct niche that is unlikely to conflict with generic git or versioning skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured commit workflow skill. It provides concrete commands at every step, includes validation checkpoints (typecheck, post-commit verification), and handles error recovery (pre-commit hook failures, type errors). Minor verbosity in the staging guidelines and some project-specific details could be tightened, but overall it's an effective and actionable skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary explanation (e.g., 'Be selective' followed by bullet points that are somewhat obvious, the parenthetical about bubble-core/bubble-runtime). The DO/DO NOT list could be tighter, but overall it's reasonably lean. | 2 / 3 |
Actionability | Provides concrete, executable commands at every step (git commands, pnpm commands, HEREDOC syntax for commit). The conventional commit format is fully specified with types, scope rules, and a concrete template. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Clear 7-step sequence with explicit validation checkpoints: typecheck in Step 4 with a 'fix before proceeding' feedback loop, pre-commit hook failure recovery in Step 6, and post-commit verification in Step 7. The workflow handles error cases (type errors, hook failures) with clear recovery instructions. | 3 / 3 |
Progressive Disclosure | For a single-purpose skill under 80 lines with no need for external references, the content is well-organized into clearly labeled sequential steps. Each section is focused and appropriately scoped. No bundle files are needed for this straightforward workflow. | 3 / 3 |
Total | 11 / 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 | |
- Repository
- bubblelabai/BubbleLab
- Commit
e64b246
- 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.