# 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:

```bash
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:

```bash
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:

```text
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.