agentleFS
sd0xdevsd0xdev/sd0x-harness/skills/bump-version/SKILL.md

bump-version

Skill192 starsChanged 37 days agoMITView on GitHub

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

42 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use oss-pr, pr-automation and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CES-LtdSkill

    oss-pr

    Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.

    Also in 3 projects that use this

  • CES-LtdSkill

    pr-automation

    PR Automation Orchestrator: poll open PRs, check CI, run review, fix, and merge eligible PRs. Use when: (1) Invoked by daemon via scripts/pr-automation.sh, (2) User says "/pr-automation".

    Also in 3 projects that use this

  • volovelySkill

    pr-fix

    This skill should be used when the user asks to "fix PR comments", "address PR feedback", "resolve PR comments", provides a GitHub PR URL with intent to fix, or says "pr-fix". It reads all review comments on a PR, decides which need code fixes vs. replies, makes the fixes, and posts replies — all with explicit user approval before any GitHub action.

    Also in 3 projects that use this

  • lbednerSkill

    i18n

    Use when a code or template change introduces a new translation message key, in either the framework CLI (aegis/i18n/locales/) or a generated project's CLI (the app/i18n/locales/ template tree). Covers adding the real English string, stubbing the same key into every other locale for parity, and the separate translation PR that later replaces placeholders with reviewed native text.

    Also in 4 projects that use this

  • NVIDIASkill

    testing

    Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.

    Also in 5 projects that use this

  • +2 more from CES-Ltd

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 38 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 8
  2. Distinctive:

    Read current versions from all files

    line 13
  3. Distinctive:

    Update all files to the same version

    line 15
  4. Very specific:

    Never bump both in one invocation: the plugin and the mod release separately, and a stray change to package.json triggers the plugin's …

    line 25
  5. Distinctive:

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

    line 42
  6. Distinctive:

    Use Edit tool to update version fields:

    line 56
  7. Distinctive:

    All must be set to the exact same version string.

    line 62
  8. Very specific:

    Run node .github/scripts/agentctl-version.js update to record the new version and the mod's digest

    line 73
  9. Distinctive:

    Never set different versions across the plugin's three files (the agentctl mod keeps its own version)

    line 93
  10. Very specific:

    Never modify other fields in the version manifests (package.json, the plugin manifests, .sd0x/install-state.json).

    line 94

“Common” is measured: kept by at least 6 in 10 of the 38 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Bump Version

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

Workflow

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

Step 0: Choose the Target

InvocationTargetSteps
/bump-version agentctl [patch|minor|major|<version>]the agentctl mod onlyStep 3b only — the plugin's three files are not read or changed, so no plugin release is triggered
anything elsethe pluginSteps 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

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

Also check manifest:

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

InputAction
Explicit version (e.g., 1.9.0)Use as-is
majorBump major: 1.8.1 → 2.0.0
minorBump minor: 1.8.1 → 1.9.0
patch (default)Bump patch: 1.8.1 → 1.8.2
No argumentDefault 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.