| name | version-bumper |
| description | Execute automatically handles semantic version updates across plugin.json and marketplace catalog when user mentions version bump, update version, or release. ensures version consistency in AI assistant-code-plugins repository. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
|
| allowed-tools | Read, Write, Edit, Grep, Bash(cmd:*) |
| version | 1.0.0 |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| license | MIT |
| compatible-with | claude-code, codex, openclaw |
| tags | ["example","version-bumper"] |
Version Bumper
Overview
Automates semantic version bumps across all version-bearing files in a Claude Code plugin. Ensures consistency between plugin.json, marketplace.extended.json, and the generated marketplace.json catalog.
Prerequisites
jq installed and available on PATH for JSON manipulation- Read/write access to
.claude-plugin/plugin.json and .claude-plugin/marketplace.extended.json
pnpm run sync-marketplace available at the repository root- Git installed for optional tag creation
Instructions
- Identify the target plugin directory and read the current version from
.claude-plugin/plugin.json using jq -r '.version'.
- Determine the bump type (major, minor, or patch) from the user request. If unspecified, infer from the nature of changes: breaking changes warrant major, new features warrant minor, and fixes warrant patch.
- Parse the current version into its
major.minor.patch components and compute the new version according to semver rules (see ${CLAUDE_SKILL_DIR}/references/version-bump-process.md).
- Update the
"version" field in .claude-plugin/plugin.json with the new version string.
- Locate the plugin entry in
.claude-plugin/marketplace.extended.json and update its "version" field to match (see ${CLAUDE_SKILL_DIR}/references/update-locations.md).
- Run
pnpm run sync-marketplace at the repository root to regenerate marketplace.json.
- Verify version consistency across all three files by reading each and confirming the version strings match.
- Optionally create a git tag (
git tag -a "v<new_version>" -m "Release v<new_version>") and prepare a commit message following the chore: Release v<version> convention (see ${CLAUDE_SKILL_DIR}/references/release-workflow.md).
Output
A version bump execution summary containing:
- The computed transition (
old_version to new_version)
- The exact files updated:
.claude-plugin/plugin.json, .claude-plugin/marketplace.extended.json, and regenerated
