How do I install the Version Bump skill?

Run npx skillmds@latest add tomevault-io/version-bump-7 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Version Bump safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Version Bump?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Version Bump free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Version Bump?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Version Bump by tomevault-io — Agent Skill

Name: Version Bump
Author: tomevault-io

Version Bump

This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Version Bump Skill

Per-plugin version bumping for the Claude Code Handbook monorepo. Each plugin can have independent versions.

When to Use This Skill

Trigger this skill when users mention:

"bump version" or "bump the version"
"increment version" or "update version numbers"
Any mention of "major", "minor", or "patch" version changes

Version Locations

Single source of truth: plugins/<name>/.claude-plugin/plugin.json

The marketplace.json is a lightweight registry (no version field) — versions live only in plugin.json.

Workflow Instructions

Step 1: List Current Versions

Show current plugin versions:

python .claude/skills/version-bump/scripts/validate_versions.py

Step 2: Ask User Which Plugin(s) to Bump

Ask the user:

Which plugin(s) to bump (can be multiple, or "all")
Which bump type: major, minor, or patch

Step 3: Execute Version Bump

Run the script with the selected plugins:

# Single plugin
python .claude/skills/version-bump/scripts/bump_version.py <bump_type> --plugin <name>

# Multiple plugins
python .claude/skills/version-bump/scripts/bump_version.py <bump_type> --plugin <name1> --plugin <name2>

# All plugins
python .claude/skills/version-bump/scripts/bump_version.py <bump_type> --all

Step 4: Report Results

After successful completion, display:

Plugins bumped with old → new versions
Next steps for git commit

CLI Reference

# Show help
python .claude/skills/version-bump/scripts/bump_version.py --help

# Error + list plugins when no --plugin flag
python .claude/skills/version-bump/scripts/bump_version.py patch

# Bump specific plugin(s)
python .claude/skills/version-bump/scripts/bump_version.py patch --plugin handbook-dotnet
python .claude/skills/version-bump/scripts/bump_version.py minor --plugin handbook --plugin handbook-extras

# Bump all plugins (legacy monorepo behavior)
python .claude/skills/version-bump/scripts/bump_version.py patch --all

Examples

Example 1: Bump Single Plugin

User: "Bump the version for handbook-dotnet"
Claude: "I'll check current versions first..."

[Runs validate_versions.py]

Claude: "handbook-dotnet is currently at 1.19.5. What bump type: major, minor, or patch?"
User: "patch"

[Runs: python bump_version.py patch --plugin handbook-dotnet]

Claude: "Done!
  handbook-dotnet: 1.19.5 → 1.19.6

Next steps:
1. git diff
2. git add . && git commit -m 'chore: bump handbook-dotnet to 1.19.6'"

Example 2: Bump Multiple Plugins

User: "Bump handbook and handbook-extras to a new minor version"

[Runs: python bump_version.py minor --plugin handbook --plugin handbook-extras]

Claude: "Done!
  handbook: 1.19.5 → 1.20.0
  handbook-extras: 1.19.5 → 1.20.0"

Example 3: Bump All Plugins

User: "Bump all plugins patch version"

[Runs: python bump_version.py patch --all]

Claude: "Done! All 13 plugins bumped from their current versions."

Notes

The script does NOT create git commits - user handles version control
Plugins can now have different versions (independent versioning)
Changelog updates are manual - user maintains CHANGELOG.md as needed

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: version-bump-7description: This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository. Use when this capability is needed.---# Version Bump SkillPer-plugin version bumping for the Claude Code Handbook monorepo. Each plugin can have independent versions.## When to Use This SkillTrigger this skill when users mention:- "bump version" or "bump the version"- "increment version" or "update version numbers"- Any mention of "major", "minor", or "patch" version changes## Version LocationsSingle source of truth: `plugins/<name>/.claude-plugin/plugin.json`The marketplace.json is a lightweight registry (no version field) — versions live only in plugin.json.## Workflow Instructions### Step 1: List Current VersionsShow current plugin versions:```bashpython .claude/skills/version-bump/scripts/validate_versions.py```### Step 2: Ask User Which Plugin(s) to BumpAsk the user:1. Which plugin(s) to bump (can be multiple, or "all")2. Which bump type: major, minor, or patch### Step 3: Execute Version BumpRun the script with the selected plugins:```bash# Single pluginpython .claude/skills/version-bump/scripts/bump_version.py <bump_type> --plugin <name># Multiple pluginspython .claude/skills/version-bump/scripts/bump_version.py <bump_type> --plugin <name1> --plugin <name2># All pluginspython .claude/skills/version-bump/scripts/bump_version.py <bump_type> --all```### Step 4: Report ResultsAfter successful completion, display:- Plugins bumped with old → new versions- Next steps for git commit## CLI Reference```bash# Show helppython .claude/skills/version-bump/scripts/bump_version.py --help# Error + list plugins when no --plugin flagpython .claude/skills/version-bump/scripts/bump_version.py patch# Bump specific plugin(s)python .claude/skills/version-bump/scripts/bump_version.py patch --plugin handbook-dotnetpython .claude/skills/version-bump/scripts/bump_version.py minor --plugin handbook --plugin handbook-extras# Bump all plugins (legacy monorepo behavior)python .claude/skills/version-bump/scripts/bump_version.py patch --all```## Examples### Example 1: Bump Single Plugin```User: "Bump the version for handbook-dotnet"Claude: "I'll check current versions first..."[Runs validate_versions.py]Claude: "handbook-dotnet is currently at 1.19.5. What bump type: major, minor, or patch?"User: "patch"[Runs: python bump_version.py patch --plugin handbook-dotnet]Claude: "Done! handbook-dotnet: 1.19.5 → 1.19.6Next steps:1. git diff2. git add . && git commit -m 'chore: bump handbook-dotnet to 1.19.6'"```### Example 2: Bump Multiple Plugins```User: "Bump handbook and handbook-extras to a new minor version"[Runs: python bump_version.py minor --plugin handbook --plugin handbook-extras]Claude: "Done! handbook: 1.19.5 → 1.20.0 handbook-extras: 1.19.5 → 1.20.0"```### Example 3: Bump All Plugins```User: "Bump all plugins patch version"[Runs: python bump_version.py patch --all]Claude: "Done! All 13 plugins bumped from their current versions."```## Notes- The script does NOT create git commits - user handles version control- Plugins can now have different versions (independent versioning)- Changelog updates are manual - user maintains CHANGELOG.md as needed---> Converted and distributed by [TomeVault](https://tomevault.io/claim/nikiforovall) — claim your Tome and manage your conversions.

Frequently asked questions