release-bump

Use this skill to finalize a release. It stamps the [Unreleased] changelog section with a version and date, runs bumpversion to update all version files, and creates the release commit and tag. Only run this when you're ready to ship.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable release workflow with strong validation and error-recovery guidance appropriate to its destructive/batch nature. The chief weaknesses are minor verbosity and a changelog-edit step that leans on placeholders rather than a fully executable command.

Suggestions

Replace the placeholder-based changelog-stamping instructions with a concrete executable edit (e.g. a sed/python one-liner) or a small bundled script to make the core action fully copy-paste ready.

Trim the explanatory restatements of bumpversion's behavior to lift conciseness toward lean efficiency.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with no generic concept padding, but a few operationally-adjacent explanations (e.g. 'The --allow-dirty flag is needed because CHANGELOG.md is already staged' and the re-list of bumpversion's behavior) could be trimmed.	4 / 5
Actionability	Concrete executable commands appear throughout (git status --porcelain, bumpversion --allow-dirty, git show --name-only --stat HEAD, recovery commands), but the changelog-stamping step uses placeholders and a manual Read/Compute/Replace flow rather than a fully copy-paste-ready edit command.	4 / 5
Workflow Clarity	A clear 7-step sequence with an explicit validation checkpoint (step 6 'Verify results' with a file checklist), pre-flight cleanliness gating, and a dedicated Error Recovery section with feedback loops — appropriate validation for a destructive batch version-bump operation.	5 / 5
Progressive Disclosure	No bundle files exist and the body makes no file references; content is organized into clean sections (Goal, Prerequisites, Workflow, Error Recovery, Notes) and is appropriately self-contained, with only minor organization gaps in the slightly long single-file form.	4 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states what the skill does and when to use it, with concrete actions and a distinct niche. The main weakness is the 'when' clause, which is a generic readiness statement rather than varied concrete trigger phrases.

Suggestions

Expand the trigger surface with concrete phrases users would say, e.g. 'Use when finalizing a release, bumping the version, or cutting a tag' to raise trigger_term_quality and completeness.

Add common synonyms like 'publish', 'cut a release', or 'tag a release' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the release-finalization domain plus multiple concrete actions — 'stamps the [Unreleased] changelog section with a version and date, runs bumpversion to update all version files, and creates the release commit and tag' — giving comprehensive coverage with no gaps.	5 / 5
Completeness	Both 'what' (stamp changelog, run bumpversion, create commit and tag) and 'when' ('Only run this when you're ready to ship') are present, but the 'when' is a single generic readiness clause rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('finalize a release', 'ready to ship', 'release') but misses common synonyms like 'cut a release', 'publish', or 'tag a release', so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche (changelog stamping + bumpversion + release tag) and explicitly distinguished from the adjacent draft-release-notes skill, giving minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jamiepine/voicebox
Path: .agents/skills/release-bump/SKILL.md
Commit: 51f49de

Reviewed: ~1 month 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.