Version Bump

When to use

Use before pushing changes in a Claude Code plugin marketplace — any repo with a .claude-plugin/marketplace.json at its root. It catches plugins whose files changed but whose version didn’t, so installers can tell when an update is available. In a non-marketplace repo the skill stays out of the way entirely.

How it works

1. Diffs the branch against its upstream (or the default branch, for a new branch) and extracts the plugin names under plugins/<name>/...
2. Reads the current version from both plugins/<name>/.claude-plugin/plugin.json and .claude-plugin/marketplace.json, flagging any drift between them
3. Reads the actual diff to categorize the change:
   • Patch — typo fixes, wording, metadata and description updates
   • Minor — new skills, new reference files or agents, significant additions
   • Major — renamed or removed skills, changed invocation names, restructured layout
4. Presents each plugin with its current version, a summary of what changed, the suggested level and reasoning, and the resulting version — then waits for you to confirm or override
5. Asks which files to write: plugin.json only, marketplace.json only, or both. It never assumes both.
6. Commits the version files as chore: bump <plugin> to <version> and proceeds with the push

Each changed plugin is handled separately, so they can take different bump levels. If no plugin files changed, or you decline the bumps, the push goes ahead untouched.

Invoke

Triggers automatically when you push in a marketplace project, or invoke manually:

/version-bump:version-bump