commit

Stage and commit changes following conventional commits. Auto-bumps package versions before committing.

1.11x

Quality

80%

Does it follow best practices?

Impact

90%

1.11x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/commit/SKILL.md

Quality

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 formatting 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

92%

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 clear sequential steps with executable commands, includes important validation checkpoints (typecheck, post-commit verification), and handles error recovery (pre-commit hook failures). The content is concise and assumes Claude's competence while providing project-specific details that Claude wouldn't otherwise know (version bumping, HEREDOC format preference, co-author line).

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient. Every section serves a purpose, there's no explanation of what conventional commits are conceptually, and instructions are direct. Minor verbosity in Step 3 bullet points but overall very token-efficient.	3 / 3
Actionability	Provides specific, executable commands at each step (git status, pnpm run bump-versions, pnpm run typecheck, git commit with HEREDOC syntax). Includes concrete commit message format with types, scope examples, and rules. Copy-paste ready.	3 / 3
Workflow Clarity	Clear 7-step sequential workflow 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 (typecheck failure, hook failure) with clear recovery instructions.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections, but everything is inline in a single file. Step 7 references a 'publish workflow' without linking to it. For a skill of this length (~70 lines of content), this is acceptable but could benefit from linking to a separate reference for conventional commit types or the publish workflow.	2 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

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: 1a11b95

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.