How do I install the Version skill?

Run npx skillmds@latest add sergio-bershadsky/version in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Version safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Version?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Version free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Version?

sergio-bershadsky (@sergio-bershadsky) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Version by sergio-bershadsky — Agent Skill

Name: Version
Author: sergio-bershadsky

Version

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 version", "/version". Updates plugin.json and marketplace.json. Creates git tag and commit.

File contents

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.

---name: versiondescription: 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 version", "/version". Updates plugin.json and marketplace.json. Creates git tag and commit.---# Version SkillBump 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 PluginIf plugin name not provided:1. Check if cwd is inside a plugin directory2. If not, list available plugins and ask user```bashls plugins/```### Step 2: Read Current Version```bashcat plugins/<name>/.claude-plugin/plugin.json | grep version```Parse the current version (e.g., `1.2.3`).### Step 3: Calculate New VersionBased 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 ConfirmPresent 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 FilesAfter approval, update version in:1. **Plugin manifest:** ``` plugins/<name>/.claude-plugin/plugin.json ``` Update the `"version"` field.2. **Marketplace catalog:** ``` .claude-plugin/marketplace.json ``` Update the version for this plugin in the `plugins` array.### Step 6: Create Git Commit and Tag```bashgit add plugins/<name>/.claude-plugin/plugin.json .claude-plugin/marketplace.jsongit 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```bashgit log -1 --onelinegit tag -l "v*-<name>" | tail -1```## Rules1. **NEVER push** — Only commit and tag locally, never push2. **ALWAYS confirm** — Never bump without user approval3. **Semantic versioning** — Follow MAJOR.MINOR.PATCH strictly4. **Update both files** — plugin.json AND marketplace.json5. **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-gitRun `git push --follow-tags` to publish.```

Frequently asked questions