release

Release Plugin Command

Release a specific plugin using the namespace@version tag pattern.

Current Context

• Working directory: !pwd
• Current branch: !git branch --show-current
• Git status: !git status --short
• Available plugins: !ls -1 plugins/

Your Task

Create a release for a specific plugin using the <plugin-name>@<version> tag pattern (e.g., [email protected]).

Prerequisites Verification

Before proceeding, verify:

1. Clean working directory: No uncommitted changes (unless they're the release commit itself)
2. Correct branch: On main branch (or ask user to confirm if on a different branch)
3. All tests pass: Run tests for the plugin being released

Release Process

Phase 1: Information Gathering

1. List available plugins from plugins/ directory
2. Ask user which plugin to release (if not obvious from context)
3. Read current version from plugins/<plugin>/package.json
4. Ask user for new version:
   • Show current version
   • Suggest semver bumps:
     • Patch: x.y.z → x.y.z+1 (bug fixes)
     • Minor: x.y.z → x.y+1.0 (new features, backward compatible)
     • Major: x.y.z → x+1.0.0 (breaking changes)
   • Allow custom version input
5. Validate version:
   • Must be valid semver (e.g., 1.0.0, 2.1.0-beta.1)
   • Check tag doesn't already exist: git tag -l "<plugin>@<version>"
6. Ask for changelog entry or offer to generate from recent commits

Phase 2: Update Version Files

Update version in exactly 3 files (atomically):

1. plugins/<plugin>/package.json:

   {
     "version": "<new-version>"
   }
   

2. plugins/<plugin>/.claude-plugin/plugin.json:

   {
     "version": "<new-version>"
   }
   

3. .claude-plugin/marketplace.json: Update the specific plugin's version in the plugins array:

   {
     "plugins": [
       {
         "name": "<plugin>",
         "version": "<new-version>",
         ...
       }
     ]
   }