Skip to content
Skills Library
Programming · Automation

version

/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.

Repository
ai ↗
Licence
Unlicense
Last repository change
17.08.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 17.08.2026, without references to retired models or APIs.

Licence

Unlicense, otwarta.

What it does and when to use it

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.

Triggers from the description

bump versionbump the versionversion bumprelease versiontag a releasecreate releasemajor/minor/patch bumpupdate version
Original author description

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.

How it works

  1. When to Use
  2. Arguments
  3. Procedure
  4. Rules
  5. Output Format
Original SKILL.md headings · 133 lines, 365 words
SKILL.md preview
---
name: version
description: |
  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 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:
1. Check if cwd is inside a plugin directory
2. If not, list available plugins and ask user

```bash
ls plugins/
```

### Step 2: Read Current Version

```bash
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:

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

```bash
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

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

## Rules

1. **NEVER push** — Only commit and tag locally, never push
2. **ALWAYS confirm** — Never bump without user approval
3. **Semantic versioning** — Follow MAJOR.MINOR.PATCH strictly
4. **Update both files** — plugin.json AND marketplace.json
5. **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.
```

Versions

The database has no other skills named version.

Database snapshot: 13.11.2026 · package version 87780d7fb274 (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-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…
  • 100version-release
    Use when bumping version, creating a release tag, or pushing a version tag. Triggers on "version up", "release", "tag push", "bump version".
  • 100release
    Cut a new release: group Conventional Commits since the last tag, append a CHANGELOG section, create a release commit, and add an annotated git tag. TRIGGER when the user says "cut a release", "tag a release", "release v1.2.0", "ship version 1.2.0", "create a release for 1.2.0",…
  • 100version-bump
    Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the…
  • 100bump-version
    Use when the user asks to tag, release, or bump the version of the sci-brain plugin (e.g. "tag a version", "cut a release", "bump to 0.3.0", "release v0.x"). Handles the three-manifest version sync, commit, annotated tag, push, and GitHub release.
  • 90bump
    This skill should be used when the user asks to "bump version", "bump new version", "release new version", "update version", "create a release", or any task involving incrementing the crux-hive plugin version, updating the changelog, and creating a release PR.

Feedback and reports

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