version-bump
/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.
- Author
- NikiforovAll ↗
- Repository
- claude-code-rules ↗
- Licence
- Apache-2.0
- Last repository change
- 02.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 2
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 02.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 2 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/bump_version.py, scripts/validate_versions.py
What it does and when to use it
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.
Original author description
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.
How it works
- When to Use This Skill
- Version Locations
- Workflow Instructions
- CLI Reference
- Examples
- Notes
SKILL.md preview
--- name: version-bump description: 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. --- # 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: ```bash python .claude/skills/version-bump/scripts/validate_versions.py ``` ### Step 2: Ask User Which Plugin(s) to Bump Ask 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 Bump Run the script with the selected plugins: ```bash # 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 ```bash # 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
Files in this package (4)
- SKILL.md 3 KB
- scripts/.gitignore 1 KB
- scripts/bump_version.py 8 KB
- scripts/validate_versions.py 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · NikiforovAll/claude-code-rules | 100 | Apache-2.0 |
| thedotmack/claude-mem | 100 | Apache-2.0 |
| meteor/meteor | 100 | MIT |
| bostonaholic/team | 100 | MIT |
| fabiensalles/claude-marketplace | 100 | MIT |
| firstloophq/nomendex | 100 | MIT |
Database snapshot: 13.11.2026 · package version 510be15a97fc (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100bump-sdk-version
Bump the FutureSearch SDK version across all files. Use when releasing a new SDK version, updating version numbers, or the user says bump version, release, version bump. - 100bump-version
Use when the user asks to bump, set or raise the duolog version, or to prepare a release commit. Do not use to only check the version; check-version does that. Do not use to create a tag or publish a release. - 100version
This skill should be used when the user wants to bump versions, create releases, or tag versions. Triggers include: "bump version", "bump the version", "version bump", "release version", "tag a release", "create release", "major/minor/patch bump", "update version", "new… - 100edit-plugin
Automates agent-skills plugin version bumps and release metadata. Use when: adding/removing/updating skills or commands, bumping plugin version, preparing a release. Triggers: bump version, edit plugin, update plugin, release, version bump, new skill added, new command added. - 86bump-version
Bump plugin version. Use when you need to increment a plugin's version number. - 100prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run `/prepare-release`.