bump-version

Automate semantic version bumps for CLAUDE-PLUGINS and update changelogs.

Updated Feb 28, 2026

Search Tags:#changelog #semver #plugin release #version bump #developer tooling #cache reinstall

Ready to run

npx skills add https://github.com/cosmicdreams/claude-plugins --skill bump-version-cosmicdreams

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/cosmicdreams/claude-plugins/tree/main/admin/skills/bump-version
Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill bump-version-cosmicdreams

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, python3, and includes scripts (resource) components.

What problem does it solve?

This Skill removes the guesswork and manual labor of releasing updated CLAUDE-PLUGINS by consistently bumping versions, updating references, writing changelogs, and reinstalling cleanly.

Core Features & Use Cases

SemVer-based version bumping: Supports major/minor/patch rules based on change type (API-breaking vs new feature vs bug/doc/script fix).
Repo-wide reference updates: Updates hardcoded version references throughout the plugin directory after the version number changes.
User-facing release notes: Prepends a new CHANGELOG section to the plugin’s CHANGELOG.md in a Claude Code-friendly format.
Clean reinstall with cache wipe: Removes cached installed versions first, then reinstalls so stale versions cannot linger.

Quick Start

Ask the skill to bump the version for a specific plugin after you finish changes, for example: "bump version for sprint as a patch".

Frequently Asked Questions about bump-version

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate semantic version bumps for plugin releases?▼

You can automate semantic version bumps by running a bash and python3 script that applies SemVer rules, updates hardcoded version references across the plugin directory, and generates changelog entries for your release.

How do I update changelog entries when releasing a new plugin version?▼

The bump process prepends a new CHANGELOG section to the plugin's CHANGELOG.md in a Claude Code-friendly format, documenting release notes for bug fixes, new features, or breaking API updates.

Why do I need to run the reinstall script outside an active Claude Code session?▼

Running the reinstall script outside an active session safely wipes cached installed versions and reinstalls from local source, preventing stale versions from lingering in your developer tooling environment.

Can I bump versions for multiple plugins at once or do I need to specify each one?▼

The bump script supports versioning either one specific plugin or all plugins at once, applying appropriate major, minor, or patch bumps based on the type of changes implemented across your plugin directory.

What's the best way to handle version references across a plugin directory during a release?▼

The bump workflow automatically updates hardcoded version references repo-wide after changing the version number, ensuring all references stay consistent without requiring manual search and replace operations.

Do I need bash and python3 installed to run the version bump workflow?▼

Yes, bash and python3 are required dependencies that execute the bump and reinstall scripts, handling SemVer calculations, reference updates, changelog generation, and cache wiping for clean reinstalls.