prepare-release

Execution Process

Step 1: Version Reset

1.1 Fetch Remote Version

bash

git fetch origin main

1.2 Check Which Plugins Have Modifications

bash

git diff --name-only origin/main -- plugins/

Determine which plugin directories have changes based on the output. Only plugins with changes need version updates.

1.3 Read Production Version Numbers

Get the marketplace version of origin/main and the versions of modified plugins:

bash

# Marketplace version
git show origin/main:.claude-plugin/marketplace.json | jq -r '.metadata.version'

# Specified plugin version
git show origin/main:.claude-plugin/marketplace.json | jq -r '.plugins[] | select(.name=="<plugin>") | .version'

1.4 Calculate New Version Number

Increment the patch version of the obtained production version by 1.

Examples:

Production marketplace:
```
0.1.10
```
→ Reset to
```
0.1.11
```
Production sync:
```
0.1.10
```
→ Reset to
```
0.1.11
```

1.5 Update Version Files

Only update plugins with changes:

.claude-plugin/marketplace.json

```
metadata.version
```
(always update)
```
version
```
of plugins with changes

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

Only update plugins with changes

Plugins without changes retain their original versions.

Important: Only plugins registered in

.claude-plugin/marketplace.json

are involved in version reset. Unregistered plugins in local development (such as ralph, etc.) need to have their entries removed from marketplace.json first, or be ignored directly.

Step 2: Update CHANGELOG.md

Insert the new version entry at the top of the file (right after the

# Changelog

heading).

Format

markdown

## {marketplace_version}

### {Plugin Name} ({plugin_version})

- Added ...
- Changed ...
- Fixed ...

### Marketplace

- Bumped version from {old_marketplace_version} to {new_marketplace_version}
- Updated {plugin} plugin to version {plugin_version}

Rules

One sub-section for each plugin with version changes:
```
### {Plugin Name} ({plugin_version})
```
- Plugin Name uses capitalized first letters + " Plugin" suffix, such as
```
Sync Plugin
```
  ,
```
Git Plugin
```

Use

git log origin/main..HEAD -- plugins/{name}/

to get the change summary for the plugin

Must write entries in English (use prefixes like Added/Changed/Fixed/Cleaned up/Updated, etc.)
Add a
```
### Marketplace
```
section at the end, listing bumped version and updated plugins

Step 3: Update Plugin README Version History

For each plugin with version changes:

Read its
```
plugins/{name}/README.md
```
Check if the
```
## 版本历史
```
(Version History) section exists
If it exists, insert the new entry at the top of this section (immediately after
```
## 版本历史
```
)

Format

markdown

- **v{version}** - {Chinese summary, separated by semicolons}

Example:

markdown

- **v0.1.12** - Added XXX command; fixed YYY issue; updated ZZZ configuration

Only process READMEs with the
## 版本历史
section, skip those without it.

Step 4: Update Root Directory README.md

Update the version numbers of plugins with version changes in the

## Plugin List

table.

Table format reference:

markdown

| Plugin   | Version | Description                                                                |
| ------- | ----- | ----------------------------------------------------------------- |
| sync    | 0.1.12 | Development environment configuration sync plugin (...) |

Only update rows with version changes, keep other rows unchanged.

Step 5: Verification

Verify the consistency of version numbers in the following locations one by one:

metadata.version

.claude-plugin/marketplace.json

```
version
```
of each plugin in
```
.claude-plugin/marketplace.json
```

version

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

Version number in the top entry of CHANGELOG.md
Version number of plugins with changes in the plugin list table in root directory README.md
Version number in the top entry of the version history in each plugin's README.md (if exists)

Output the verification result table for user confirmation:

| Location                      | Plugin | Version | Status |
| ----------------------------- | ------ | ------ | ---- |
| marketplace.json (metadata)   | -      | 0.1.16 | ✅   |
| marketplace.json (plugin)     | sync   | 0.1.12 | ✅   |
| plugin.json                   | sync   | 0.1.12 | ✅   |
| CHANGELOG.md                  | sync   | 0.1.12 | ✅   |
| README.md (root)              | sync   | 0.1.12 | ✅   |
| README.md (plugin)            | sync   | 0.1.12 | ✅   |

prepare-release

NPX Install

Tags

SKILL.md Content (Chinese)

Execution Process

Step 1: Version Reset

1.1 Fetch Remote Version

1.2 Check Which Plugins Have Modifications

1.3 Read Production Version Numbers

1.4 Calculate New Version Number

1.5 Update Version Files

Step 2: Update CHANGELOG.md

Format

Rules

Step 3: Update Plugin README Version History

Format

Step 4: Update Root Directory README.md

Step 5: Verification