release-bump
Increment version numbers, update changelogs, and verify changes before final tagging.
Install
mkdir -p .claude/skills/release-bump-synthet && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16496" && unzip -o skill.zip -d .claude/skills/release-bump-synthet && rm skill.zipInstalls to .claude/skills/release-bump-synthet
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Bump the project version with a semver rubric, promote the Unreleased changelog section, and verify before committing. Use when the user asks to cut a release, bump the version, or tag a new version.Key capabilities
- →Detect the version source in the project
- →Choose the appropriate semver bump level (major, minor, patch)
- →Update the version in the detected source file
- →Rename `## [Unreleased]` to the new version in `CHANGELOG.md`
- →Add a fresh empty `## [Unreleased]` section
- →Run verification checks from AGENTS.md
How it works
The skill identifies the version source, determines the semver bump based on changes, updates the version and changelog, and then runs verification checks before preparing a commit.
Inputs & outputs
When to use release-bump
- →Bump project version
- →Cut a release
- →Tag new release
About this skill
Release bump (compiled harness)
Thin bootloader. Deterministic work lives in the harness; you only decide the semver level.
Invoke
# Inspect current version + Unreleased bullets (no writes)
python .claude/skills/release-bump/scripts/harness.py --json
# After choosing major|minor|patch, apply VERSION + CHANGELOG
python .claude/skills/release-bump/scripts/harness.py --level minor --apply --json
LLM judgment slots
- Choose bump level from
git log <last-tag>..HEADand harnessunreleased_bullets:- major — breaking API/config/schema/CLI/MCP/autotile contract change
- minor — backward-compatible capability
- patch — bug fix, docs, internal refactor
- State the level and 1–2 justifying changes, then pass
--level.
If the harness reports no version source, ask the user before creating VERSION /
CHANGELOG.md. Unity bundle version in ProjectSettings is a human Editor workflow,
not this harness.
Human authority
Do not commit, tag, or push unless the user explicitly asks. Suggest
chore(release): vX.Y.Z and annotated tag only after verify commands succeed.
Verify
Run every command listed in harness verify_commands (and check_paid_assets.py /
check_markdown_links.py as listed) before any release commit.
When not to use it
- →When no semver source exists and the user has not approved creating one
- →When the user does not want to bump the version
- →When the user does not want to update the changelog
Limitations
- →Requires a detectable version source or user approval to create one
- →Relies on `CHANGELOG.md` for changelog updates
- →Does not commit, tag, or push without explicit user request
How it compares
This skill automates the semver-compliant version bumping and changelog update process, ensuring consistency and verification, unlike manual updates that can be error-prone.
Compared to similar skills
release-bump side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release-bump (this skill) | 0 | 1mo | Review | Intermediate |
| gcp-cloud-run | 5 | 5mo | Review | Intermediate |
| flow-nexus-platform | 6 | 4mo | Review | Beginner |
| smithery-mcp-deployment | 8 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
smithery-mcp-deployment
CaullenOmdahl
Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
netlify-deploy
openai
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.