Skill

bump-plugin-version

This skill should be used when the user asks to "bump plugin version", "update plugin version", "release new version", "increment version", or "tag a new release" in a Claude Code plugin project.

npx claudepluginhub tim-hub/powerball

Configuration

Model: haiku

Tool Access

This skill is limited to using the following tools:

BashRead

Preview

Use the provided argument as the name of the specific plugin to bump. Only process that plugin's entry in `marketplace.json` (and its `plugin.json` if `strict` applies). If no argument is given, process all plugins in `marketplace.json`.

SKILL.md

Similar Skills

version-bumper

1.9k

Automates semver bumps for Claude Code plugins: updates plugin.json and marketplace.extended.json, regenerates marketplace.json, verifies consistency, preps git tags.

10 files5 tools

jeremy-plugin-tool

claude-code-plugin-release

72.1k

Automates semantic versioning and release workflow for Claude Code plugins: updates package.json and manifests, npm publishes for npx resolution, verifies builds, git tags, creates GitHub releases, generates changelog.

1 file

claude-mem

using-superpowers

178.4k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Parent Repo Stars2

Parent Repo Forks0

Last CommitMar 23, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Argument: plugin name (optional)

Use the provided argument as the name of the specific plugin to bump. Only process that plugin's entry in marketplace.json (and its plugin.json if strict applies). If no argument is given, process all plugins in marketplace.json.

Step 1: Check for marketplace.json

Check if .claude-plugin/marketplace.json exists.

If it does not exist: fall back to the single-plugin flow — read .claude-plugin/plugin.json for the target plugin, bump its version, then skip to Step 3.

Step 2: Determine bump scope per plugin

For the target plugin entry in marketplace.json, check whether strict is false:

If strict is false: the plugin version in marketplace.json is decoupled from the plugin's own plugin.json. Bump the version only in marketplace.json.
If strict is true (or not set): versions must stay in sync. Go to the plugin's folder, find its plugin.json, bump the version there, then update marketplace.json to match.

Step 3: Commit and tag

Run the powerball-core:commit skill to commit the changes.
Run the powerball-core:tag skill to tag git with the same version that was bumped.