- Home
- Skills
- Nikiforovall
- Claude Code Rules
- Version Bump
version-bump_skill
83
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill nikiforovall/claude-code-rules --skill version-bump- SKILL.md3.5 KB
Overview
This skill automates per-plugin version bumps for the Claude Code Handbook monorepo. It updates the two source locations that must stay in sync and reports the before/after values. Use it during release prep to increment major, minor, or patch versions across one, many, or all plugins.
How this skill works
The skill inspects plugin version fields in .claude-plugin/marketplace.json and plugins/<name>/.claude-plugin/plugin.json to ensure consistency. It runs a validation step to list current versions, prompts which plugin(s) and bump type to apply, then executes the bump script to update files. After running, it summarizes old → new versions and shows git next steps (it does not commit).
When to use it
- Preparing a release and you need to increment plugin versions
- When a user asks to bump, increment, or update a plugin version
- After merging feature work that requires a major/minor/patch change
- When synchronizing versions across multiple plugins in the monorepo
- When you want to bump all plugins at once for a coordinated release
Best practices
- Run the validation script first to list current versions: python .claude/skills/version-bump/scripts/validate_versions.py
- Decide bump type (major, minor, patch) before executing the bump for predictable results
- Bump only the plugins that changed; use --all sparingly for coordinated releases
- Review git diff and create a descriptive commit message; the script does not commit automatically
- Manually update changelogs if your release process requires changelog entries
Example use cases
- Bump a single plugin patch: check versions, choose handbook-dotnet, run bump_version.py patch --plugin handbook-dotnet
- Bump multiple plugins for a minor release: bump_version.py minor --plugin handbook --plugin handbook-extras
- Bump all plugins after a repository-wide fix: bump_version.py patch --all and then commit the changes
- Validate versions before any bump to catch mismatches with python .claude/skills/version-bump/scripts/validate_versions.py
FAQ
No. The script updates version files only. You must git add and commit the changes yourself.
Which files are updated when a version is bumped?
It updates the plugin entry in .claude-plugin/marketplace.json and the plugin's plugins/<name>/.claude-plugin/plugin.json to keep them in sync.