Skip to content
Skills Library
Programming · Automation

bump-version

/bump-version

Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says 'bump version', 'update version', '更新版本', '版本 +1', or /bump-version

Licence
MIT
Last repository change
08.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says 'bump version', 'update version', '更新版本', '版本 +1', or /bump-version

Triggers from the description

bump versionupdate version更新版本版本 +1
Original author description

Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says 'bump version', 'update version', '更新版本', '版本 +1', or /bump-version

How it works

  1. Workflow
  2. Step 0: Choose the Target
  3. Step 1: Read Current Versions
  4. Step 2: Determine New Version
  5. Step 3: Update All Files
  6. Step 3b: The agentctl mod (/bump-version agentctl, only where mods/agentctl/ exists)
  7. Step 4: Report
  8. Prohibited
Original SKILL.md headings · 91 lines, 524 words
SKILL.md preview
---
name: bump-version
description: "Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says 'bump version', 'update version', '更新版本', '版本 +1', or /bump-version"
---

# Bump Version

Update `package.json`, `.claude-plugin/plugin.json`, and `.sd0x/install-state.json` versions in sync.

## Workflow

0. Choose the target (below) — the plugin, or the agentctl mod
1. Read current versions from all files
2. Determine new version (from argument or auto-increment)
3. Update all files to the same version
4. Report result

## Step 0: Choose the Target

| Invocation | Target | Steps |
|------------|--------|-------|
| `/bump-version agentctl [patch\|minor\|major\|<version>]` | the agentctl mod only | **Step 3b only** — the plugin's three files are not read or changed, so no plugin release is triggered |
| anything else | the plugin | Steps 1–4; Step 3b is not run |

Never bump both in one invocation: the plugin and the mod release separately, and a stray change to
`package.json` triggers the plugin's release workflow. When the plugin is bumped and
`node .github/scripts/agentctl-version.js check` reports that the mod changed too, say so and suggest
`/bump-version agentctl` as a separate run.

## Step 1: Read Current Versions

```bash
grep '"version"' package.json .claude-plugin/plugin.json
```

Also check manifest:

```bash
grep '"plugin_version"' .sd0x/install-state.json 2>/dev/null || echo "(no manifest)"
```

If versions are already out of sync, warn user before proceeding.

## Step 2: Determine New Version

| Input | Action |
|-------|--------|
| Explicit version (e.g., `1.9.0`) | Use as-is |
| `major` | Bump major: `1.8.1` → `2.0.0` |
| `minor` | Bump minor: `1.8.1` → `1.9.0` |
| `patch` (default) | Bump patch: `1.8.1` → `1.8.2` |
| No argument | Default to `patch` |

## Step 3: Update All Files

Use Edit tool to update version fields:

1. `package.json` — `"version"` field
2. `.claude-plugin/plugin.json` — `"version"` field
3. `.sd0x/install-state.json` — `"plugin_version"` field (if file exists)

All must be set to the **exact same version string**.

The manifest update prevents the SessionStart drift sentinel from firing false warnings after every version bump in the plugin source repo.

## Step 3b: The agentctl mod (`/bump-version agentctl`, only where `mods/agentctl/` exists)

The mod is versioned separately and released under `agentctl-v<version>` tags. This step runs **instead
of** Steps 1–3, never after them, and only where `mods/agentctl/.claude-plugin/plugin.json` exists:

1. Bump `"version"` in `mods/agentctl/.claude-plugin/plugin.json` by the Step 2 rules applied to the
   argument after `agentctl`, from **its own** current version — never to the plugin's version
2. Run `node .github/scripts/agentctl-version.js update` to record the new version and the mod's digest

Claude Code caches an installed plugin by version, so a mod change shipped under an unchanged version can
miss everyone who already installed it; CI fails until the lock is recorded.

## Step 4: Report

```
## Version Bump

| File | Field | Before | After |
|------|-------|--------|-------|
| package.json | version | x.y.z | a.b.c |
| .claude-plugin/plugin.json | version | x.y.z | a.b.c |
| .sd0x/install-state.json | plugin_version | x.y.z | a.b.c |
| mods/agentctl/.claude-plugin/plugin.json | version (only when bumped) | p.q.r | p.q.s |
```

## Prohibited

- Never set different versions across the plugin's three files (the agentctl mod keeps its own version)
- Never modify other fields in the version manifests (`package.json`, the plugin manifests, `.sd0x/install-state.json`); `mods/agentctl/release.json` is generated and is written only by `agentctl-version.js update`

Versions

RepositoryScoreLicence
This page · sd0xdev/sd0x-harness100MIT
membrowse/membrowse-action100GPL-3.0
lorem-dev/duolog100Apache-2.0
waldekmastykarz/vally-claudecodecli100MIT
cassandragargoyle/skill-source-trust-assessment100MIT
iofficeai/aionui100Apache-2.0
ChandraChaan/flutter-release-kit100MIT
hyhmrright/logic-lens100MIT
quantumbfs/sci-brain100MIT

Database snapshot: 13.11.2026 · package version 698f25fdbdc8 (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

  • 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…
  • 100prepare-package-release
    Prepare and validate Rudder plugin version bumps, including synchronized package/plugin manifests and a CodeAlmanac wiki refresh. Use whenever changing the version in package.json, package-lock.json, .codex-plugin/plugin.json, .claude-plugin/plugin.json, or…
  • 100nx-gradle-plugin-version-bump
    Bump the dev.nx.gradle.project-graph plugin version. Use when updating the Gradle project graph plugin version across the codebase, creating the migration files, and updating migrations.json.
  • 100version-bump
    ACTIVATE before every `gh pr create` / `gh pr edit` in the claude-marketplace repo, and before any commit that touches files under plugins/. ACTIVATE for 'bump version', 'bump les versions', 'release plugin', 'version bump', 'semver', 'mets à jour les versions'. Classifies the…
  • 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.
  • 100obsidian-plugin-release
    Release a new version of an Obsidian community plugin without forgetting steps. Use when: (1) user says "release the plugin", "bump <plugin> to X.Y.Z", "ship a new Obsidian release", "tag a new plugin version", "publish to the obsidian directory", (2) the working directory…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.