version

Bump semantic versions for plugins with git tag and commit.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "version" with this command: npx skills add sergio-bershadsky/ai/sergio-bershadsky-ai-version

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.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

frappe-doctype

No summary provided by upstream source.

Repository SourceNeeds Review
General

frappe-service

No summary provided by upstream source.

Repository SourceNeeds Review
General

frappe-app

No summary provided by upstream source.

Repository SourceNeeds Review
General

frappe-api

No summary provided by upstream source.

Repository SourceNeeds Review