meta-mcp: Skill for Claude Code

Release meta-mcp

You are releasing version $ARGUMENTS of meta-mcp.

If no version is provided, ask the user for the target version number (semver: X.Y.Z).

This workflow works best with extended thinking enabled — version bump validation benefits from careful checking.

Step 1: Validate Prerequisites

Create tasks to track progress. Run these checks first — if any fail, stop and explain what's wrong.

1. Branch check — must be on main:

   git branch --show-current
   

2. Clean working tree — no uncommitted changes:

   git status --porcelain
   

3. Synced with remote — fetch and check:

   git fetch origin main
   git rev-list --left-right --count origin/main...HEAD
   

   Left > 0 means behind remote, right > 0 means ahead. Both should be 0.

4. Tag doesn't exist yet:

   git tag -l "v$VERSION"
   gh release view "v$VERSION" 2>&1
   

Step 2: Validate and Update CHANGELOG.md

1. Read CHANGELOG.md and find the [Unreleased] section.
2. It must have content under ### Fixed, ### Changed, or ### Added — reject if empty.
3. Show the unreleased changes and use AskUserQuestion to ask for confirmation before proceeding.
4. Add a new empty ## [Unreleased] section at the top.
5. Rename the old [Unreleased] content to ## [X.Y.Z] — YYYY-MM-DD (today's date).

Step 3: Bump Version Everywhere

First, determine the current version from package.json. Then search for ALL occurrences using the Grep tool:

pattern: "CURRENT_VERSION"  (the literal current version string)
glob: "*.{json,ts,md,txt}"
exclude: node_modules/, dist/, package-lock.json

Files that typically need version bumps:

File	Location
package.json	"version": "X.Y.Z"
server.json	"version": "X.Y.Z" (appears twice)

Note: src/index.ts reads the version from package.json at runtime via createRequire — no manual bump needed there.

After finding all occurrences, update each one. Do not touch version references inside node_modules/, dist/, or package-lock.json — the lock file will be regenerated.