Skill

version

Bumps semantic versions (major/minor/patch) for Claude Code plugins, updates plugin.json and marketplace.json, creates git commit and tag. Use after features, bug fixes, or breaking changes.

Git

git-workflow

deployment

npx claudepluginhub sergio-bershadsky/ai --plugin version

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Bump semantic versions for plugins with git tag and commit.

SKILL.md

Similar Skills

version-bumper

2.1k

Automates semantic version bumps across plugin.json, marketplace.extended.json, and marketplace.json in Claude Code plugins. Triggers on mentions of version bump, update version, or release for consistency.

10 files5 tools

jeremy-plugin-tool

bump-plugin-version

Bumps Agent Alchemy plugin versions across 5 locations each, detects drift, applies updates, adds CHANGELOG entries, and creates conventional commits.

6 tools

agent-alchemy-plugin-tools

ui-ux-pro-max

76.2k

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

Stats

Parent Repo Stars11

Parent Repo Forks0

Last CommitFeb 20, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Version Skill

Bump semantic versions for plugins with git tag and commit.

When to Use

After completing a feature (minor bump)
After fixing bugs (patch bump)
After breaking changes (major bump)
Before releasing a new version

Arguments

/version [bump-type] [plugin-name]

bump-type: major, minor, or patch (default: patch) plugin-name: Plugin to version (default: auto-detect from cwd or prompt)

Examples:

/version patch git
/version minor settings-sync
/version major

Procedure

Step 1: Identify Plugin

If plugin name not provided:

Check if cwd is inside a plugin directory
If not, list available plugins and ask user

ls plugins/

Step 2: Read Current Version

cat plugins/<name>/.claude-plugin/plugin.json | grep version

Parse the current version (e.g., 1.2.3).

Step 3: Calculate New Version

Based on bump type:

major: 1.2.3 → 2.0.0
minor: 1.2.3 → 1.3.0
patch: 1.2.3 → 1.2.4

Step 4: Show Changes and Confirm

Present to user:

## Version Bump

**Plugin:** git
**Current:** 1.2.3
**New:** 1.3.0
**Type:** minor

**Files to update:**
- plugins/git/.claude-plugin/plugin.json
- .claude-plugin/marketplace.json

**Git actions:**
- Commit: "chore(git): bump version to 1.3.0"
- Tag: v1.3.0-git

---
Proceed with version bump?

Wait for user confirmation.

Step 5: Update Files

After approval, update version in:

Plugin manifest:

plugins/<name>/.claude-plugin/plugin.json

Update the "version" field.

Marketplace catalog:
```
.claude-plugin/marketplace.json
```
Update the version for this plugin in the plugins array.

Step 6: Create Git Commit and Tag

git add plugins/<name>/.claude-plugin/plugin.json .claude-plugin/marketplace.json
git commit -m "chore(<name>): bump version to <new-version>"
git tag -a "v<new-version>-<name>" -m "Release <name> v<new-version>"

Step 7: Verify

git log -1 --oneline
git tag -l "v*-<name>" | tail -1

Rules

NEVER push — Only commit and tag locally, never push
ALWAYS confirm — Never bump without user approval
Semantic versioning — Follow MAJOR.MINOR.PATCH strictly
Update both files — plugin.json AND marketplace.json
Tag format — Use v<version>-<plugin-name> for multi-plugin repos

Output Format

## Version Bump Complete

**Plugin:** git
**Version:** 1.2.3 → 1.3.0

**Commit:** abc1234 chore(git): bump version to 1.3.0
**Tag:** v1.3.0-git

Run `git push --follow-tags` to publish.