New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release Bump

by jamiepine in jamiepine/voicebox

Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

MITAuto-check passedDevelopment

Install Release Bump

skills CLI
$ npx skills add jamiepine/voicebox --skill release-bump -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jamiepine/voicebox release-bump --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jamiepine/voicebox.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-bump .claude/skills/release-bump && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release-bump
GitHub stars
57k
Token cost
~1.1k tokens
SKILL.md length
432 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

  • Works in 7 steps: Verify the working tree is clean (except… → Determine the bump level. → Stamp the changelog. → …
  • Shipping a release once the changelog draft is ready
  • SKILL.md covers Goal, Prerequisites, Workflow and Version Calculation Reference, plus 2 more sections
  • Calls git, gh and pip

What it does

The agent checks that the working tree is clean apart from CHANGELOG.md, asks for the bump level (patch, minor or major) if you did not give one, and reads the current version from .bumpversion.cfg. It then stamps the changelog: the Unreleased body moves into a new dated section for the new version, an empty Unreleased heading stays on top, and the compare links at the bottom of the file are updated.

After staging CHANGELOG.md it runs bumpversion with --allow-dirty, which updates version strings in the tracked files, creates a Bump version commit and a v-prefixed tag, and folds in the staged changelog. The agent finishes by checking the commit contents and the tag list. The result is a release commit and tag ready to push, and the skill does not push for you.

It expects gh to be authenticated, bumpversion to be installed and the Unreleased section to be filled in already. If that section is empty or stale, the draft-release-notes skill should run first.

When your agent uses it

  • Shipping a release once the changelog draft is ready
  • Bumping a patch, minor or major version across all tracked files
  • Creating a release commit and tag from the Unreleased section

Example prompts

  • “Cut a minor release: stamp the changelog and bump the version.”
  • “Bump the patch version and tag the release. The Unreleased notes are ready.”
  • “Check that the working tree is clean, then finalize the release with bumpversion.”

Requirements

  • bumpversion, with a .bumpversion.cfg in the repository
  • GitHub CLI (gh), authenticated
  • A CHANGELOG.md whose Unreleased section is already written

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Verify the working tree is clean (except CHANGELOG.md which may have the draft).
  2. Determine the bump level.
  3. Stamp the changelog.
  4. Stage the changelog.
  5. Run bumpversion.
  6. Verify results.
  7. Do NOT push unless the user explicitly asks. Report the tag name and suggest

What it can do on your machine

Read from SKILL.md and the folder at commit 8af7efe. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, gh and pip, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Bump loads about 1.1k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 432 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jamiepine/voicebox at commit 8af7efe, republished under its MIT licence (© jamiepine). 432 words, ~1,050 tokens.

Download SKILL.mdSave it as .claude/skills/release-bump/SKILL.md (or your agent's skills folder).
name
release-bump
description
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.

Release Bump

Goal

Finalize the changelog draft, bump the version across all tracked files, and create a tagged release commit. After this skill runs, the repo has a clean release commit and tag ready to push.

Prerequisites

  • gh CLI installed and authenticated (gh auth status).
  • bumpversion installed (pip install bumpversion or available in the project venv).
  • The [Unreleased] section of CHANGELOG.md should already contain the release narrative. If it's empty or stale, run the draft-release-notes skill first.

Workflow

  1. Verify the working tree is clean (except CHANGELOG.md which may have the draft).

    bash
    git status --porcelain

    Only CHANGELOG.md (and optionally .agents/ files) should be modified. If there are other uncommitted changes, stop and ask the user to commit or stash them first.

  2. Determine the bump level.

    Ask the user if not specified: patch, minor, or major. Check the current version:

    bash
    grep '^current_version' .bumpversion.cfg

  3. Stamp the changelog.

    Read the current [Unreleased] content from CHANGELOG.md. Compute the new version (based on bump level and current version). Then:

    a. Replace the ## [Unreleased] section body with an empty placeholder. b. Insert a new stamped section immediately after ## [Unreleased]:

    markdown
    ## [Unreleased]

## [X.Y.Z] - YYYY-MM-DD

<the content that was in [Unreleased]>

    c. Update the reference links at the bottom of the file:

    • Change the [Unreleased] link to compare against the new tag
    • Add a new link for the new version
    markdown
    [Unreleased]: https://github.com/jamiepine/voicebox/compare/vX.Y.Z...HEAD
[X.Y.Z]: https://github.com/jamiepine/voicebox/compare/vPREVIOUS...vX.Y.Z

  4. Stage the changelog.

    bash
    git add CHANGELOG.md

  5. Run bumpversion.

    bash
    bumpversion --allow-dirty <patch|minor|major>

    The --allow-dirty flag is needed because CHANGELOG.md is already staged. bumpversion will:

    • Update version strings in all tracked files (see .bumpversion.cfg)
    • Create a commit with message Bump version: X.Y.Z -> A.B.C
    • Create a tag vA.B.C

    The staged CHANGELOG.md will be included in this commit automatically.

  6. Verify results.

    bash
    git show --name-only --stat HEAD
git tag --list "v*" --sort=-v:refname | head -n 5

    Confirm the commit contains:

    • CHANGELOG.md
    • .bumpversion.cfg
    • tauri/src-tauri/tauri.conf.json
    • tauri/src-tauri/Cargo.toml
    • package.json
    • app/package.json
    • tauri/package.json
    • web/package.json
    • backend/__init__.py

    Confirm the new tag exists.

  7. Do NOT push unless the user explicitly asks. Report the tag name and suggest:

    Ready to push. When you're ready:
  git push origin main --follow-tags
Show full SKILL.md (137 more words)Show less

Version Calculation Reference

Given current version X.Y.Z:

  • patch -> X.Y.(Z+1)
  • minor -> X.(Y+1).0
  • major -> (X+1).0.0

Error Recovery

  • If bumpversion fails, the tag won't exist. Fix the issue and re-run — bumpversion is idempotent as long as the tag doesn't already exist.
  • If you need to undo a release commit (before pushing): git tag -d vX.Y.Z && git reset --soft HEAD~1
  • Never amend a release commit that has been pushed.

Notes

  • When the tag is pushed, the release CI (.github/workflows/release.yml) automatically extracts the matching version section from CHANGELOG.md and uses it as the GitHub Release body. No manual copy-paste needed.
  • The release commit message is controlled by .bumpversion.cfg (Bump version: X.Y.Z -> A.B.C). Do not override it.
  • If you need to manually update the GitHub Release body after the fact: gh release edit vX.Y.Z --notes-file <(sed -n '/## \[X.Y.Z\]/,/## \[/p' CHANGELOG.md | head -n -1)

© jamiepine, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/release-bump of jamiepine/voicebox.

Open the folder on GitHubat commit 8af7efe

Compare with similar skills

Release Bump next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Bump compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Bump this skilljamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Go-Redis Release Preparationredis/go-redis22k—~1.1kAutomated safety check: PassBSD-2-Clause
Hunk Release Workflowmodem-dev/hunk9.5k—~3.8kAutomated safety check: PassMIT
Worktrunk Release Workflowmax-sixty/worktrunk8.9k—~6.9kAutomated safety check: PassCustom licence
pybind11 Release Publicationpybind/pybind1118k—~2.5kAutomated safety check: PassCustom licence
Obot Release Notes Drafterobot-platform/obot1.1k—~4.5kAutomated safety check: PassMIT

Similar skills

  • Go-Redis Release Preparation

    redis/go-redis

    Official

    Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.

    22k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Hunk Release Workflow

    modem-dev/hunk

    Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.

    9.5k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Worktrunk Release Workflow

    max-sixty/worktrunk

    Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

    8.9k GitHub stars~6.9k tokensUpdated today
    DevelopmentAuto-check passed

  • pybind11 Release Publication

    pybind/pybind11

    Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release.

    18k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Obot Release Notes Drafter

    obot-platform/obot

    Drafts release notes for an upcoming Obot minor release and saves them as an unpublished GitHub draft release, never tagging or publishing.

    1.1k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed

  • GreptimeDB Release Notes

    GreptimeTeam/greptimedb

    Generates a GreptimeDB release changelog with git cliff, subtracts patch PRs already shipped, rebuilds contributors and prepares the docs-repo blog PR.

    6.7k GitHub stars~2.5k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from jamiepine/voicebox

  • Add TTS Engine to Voicebox

    jamiepine/voicebox

    Walks through adding a new text-to-speech engine to Voicebox end to end: dependency audit, backend, frontend wiring, PyInstaller bundling and frozen-build testing.

    57k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated today
    Auto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Release Bump

What does Release Bump do?

Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit. cfg. It then stamps the changelog: the Unreleased body moves into a new dated section for the new version, an empty Unreleased heading stays on top, and the compare links at the bottom of the file are updated.

When should I use Release Bump?

Release Bump fits situations like: shipping a release once the changelog draft is ready; bumping a patch, minor or major version across all tracked files; creating a release commit and tag from the Unreleased section.

How do I install Release Bump in Claude Code?

Run `npx skills add jamiepine/voicebox --skill release-bump -a claude-code`. Or copy the skill folder (.agents/skills/release-bump in jamiepine/voicebox) into .claude/skills/release-bump in your project. Claude Code loads it when a task matches its description.

How do I install Release Bump in Codex?

Run `npx skills add jamiepine/voicebox --skill release-bump -a codex`. Or copy the skill folder (.agents/skills/release-bump in jamiepine/voicebox) into .agents/skills/release-bump in your project. Codex loads it when a task matches its description.

Can I use Release Bump in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jamiepine/voicebox --skill release-bump -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-bump, .gemini/skills/release-bump, .github/skills/release-bump and .opencode/skills/release-bump in your project.

What does Release Bump need to run?

Going by SKILL.md and its folder, Release Bump needs the command-line tools its instructions call (git, gh and pip). Our summary lists: bumpversion, with a .bumpversion.cfg in the repository; GitHub CLI (gh), authenticated; A CHANGELOG.md whose Unreleased section is already written.

Does Release Bump access the network?

SKILL.md contains no URLs. Its commands use git, gh and pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release Bump safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Bump use?

Release Bump is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Bump use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Bump?

Skills that share tags, products or a category with Release Bump: Go-Redis Release Preparation (redis/go-redis, 22k stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars), Worktrunk Release Workflow (max-sixty/worktrunk, 8.9k stars) and pybind11 Release Publication (pybind/pybind11, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Bump?

jamiepine (a GitHub user) maintains it in jamiepine/voicebox, which has 56,524 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.

Source: jamiepine/voicebox on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.