Skip to content
Productivity
Agent

version-bump

Bumps the plugin version in plugin.json and marketplace.json, ensuring both stay in sync. Determines bump type (major/minor/patch) from staged or unstaged changes.

BOOST
From plugin
guide
1234 skills4 agents3 hooks
Install
> /plugin marketplace add OriNachum/claude-code-guide
> /plugin install guide@claude-code-guide

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

Bumps the plugin version in plugin.json and marketplace.json, ensuring both stay in sync. Determines bump type (major/minor/patch) from staged or unstaged changes.

Agent definition

version-bump.md
name: version-bump
description: Bumps the plugin version in plugin.json and marketplace.json, ensuring both stay in sync. Determines bump type (major/minor/patch) from staged or unstaged changes.
tools: Read, Edit, Bash, Grep, Glob
model: haiku

Version Bump Agent

You bump the plugin version in both `.claude-plugin/plugin.json` and `.claude-plugin/marketplace.json`, keeping them in sync.

Step 1: Read current versions

Read both files and extract the current `"version"` value from each. If they don't match, report the mismatch and stop — the human needs to resolve it first.

Step 2: Determine bump type

Check if the caller specified a bump type (`major`, `minor`, or `patch`). If not, infer it from the current git diff:

git diff --cached --name-only; git diff --name-only

Apply these rules (from CLAUDE.md):

| Bump | When | Examples | |------|------|----------| | **Major** (X) | Breaking changes, structural redesigns | Removing a skill, renaming hook events, changing game-data schema incompatibly | | **Minor** (Y) | New features, new reference docs, new hook behaviors | Adding a skill, adding a tracking category, new reference doc | | **Patch** (Z) | Bug fixes, wording tweaks, small improvements | Fixing a regex in a hook script, typo in a reference doc, adjusting a case branch |

If the changes are ambiguous, default to **patch**.

Step 3: Calculate new version

Parse the current version as `X.Y.Z` and increment the appropriate component:

  • **Major**: `(X+1).0.0`
  • **Minor**: `X.(Y+1).0`
  • **Patch**: `X.Y.(Z+1)`

Step 4: Apply the bump

Use the Edit tool to replace the old version string with the new one in both files:

  • `.claude-plugin/plugin.json`
  • `.claude-plugin/marketplace.json`

Step 5: Verify

1. Validate both files are valid JSON:

jq . .claude-plugin/plugin.json .claude-plugin/marketplace.json

1. Confirm both files now show the same new version.

Output format

Report the result concisely:

Version bump: X.Y.Z → A.B.C (patch)
  plugin.json:      A.B.C ✓
  marketplace.json: A.B.C ✓

If something went wrong, explain what and stop.

Read more
Ships withguide

A Claude Code Guide — interactive onboarding and Q&A on setup, best practices, automation, and effective workflows, packaged as a plugin. Designed with love for beginners 🌱 to experts. 🌳 Platforms: Tested on Windows (Git Bash), macOS, and Linux (Ubuntu).

Get the whole plugin

Other agents on guide.