release-bump

release-bump is a skill for Claude Code, Codex from jamiepine/voicebox. It costs 54 tokens per session (1,135 once invoked), scanned A, original, MIT.

A release-finalization skill that completes the [Unreleased] changelog entry, updates the software version in tracked files, and creates a release commit and version tag. A tag is a named Git reference marking a specific code state.

In plain words
What is it for?
Use it when ready to publish a patch, minor, or major release: set the version, date the changelog, update version files, and create the release commit and tag.
Why use it?
It handles the coordinated versioning work needed to ship, while stopping if unrelated uncommitted changes could make the release unsafe.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/jamiepine/voicebox/release-bump
Any agent
npx skills add jamiepine/voicebox --skill release-bump
Clone the repo
git clone --depth 1 https://github.com/jamiepine/voicebox

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for release-bump

README.md
[![agentmods](https://agentmods.dev/badge/skills/jamiepine/voicebox/release-bump.svg)](https://agentmods.dev/skills/jamiepine/voicebox/release-bump)
Your own site
<a href="https://agentmods.dev/skills/jamiepine/voicebox/release-bump"><img src="https://agentmods.dev/badge/skills/jamiepine/voicebox/release-bump.svg" alt="Measured on agentmods" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,135 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00054 $0.01135
Opus 5 $0.00027 $0.00567
Sonnet 5 $0.00011 $0.00227
Haiku 4.5 $0.00005 $0.00113

Measured 4d ago against content hash c3043ac10e5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

release-bump scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/release-bump/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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).

    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:

    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]:

    ## [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
    [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.

    git add CHANGELOG.md
    
  5. Run bumpversion.

    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

Read the full file on GitHub · 125 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 125 lines · 54 tokens per session scan A c3043ac10e5e

Subscribe to this mod's changes

release-bump is a skill published in the GitHub repository jamiepine/voicebox (52,058 stars, last pushed 25d ago), licensed MIT. It adds 54 tokens to every session and 1,135 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

release

Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.

openai/symphony · 42 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

snapshot-release

Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …

daangn/seed-design · 142 tokens

multi-repo-release

Prepares and validates GPT-RAG umbrella releases across component repositories and the AI Landing Zone. Use for manifest pins, changelog entries, release branches, tags, and GitHub Release notes.

Azure/GPT-RAG · 43 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens