SuperSpec: Skill for Cursor

Changeset Release

Manage the full release lifecycle for this pnpm monorepo using @changesets/cli.

Project Context

• Monorepo root: project root with pnpm-workspace.yaml
• Package manager: pnpm
• Packages: packages/cli → @superspec/cli
• Changeset config: .changeset/config.json (access: public, baseBranch: master)
• NPM auth: user-level ~/.npmrc with token

Commands Reference

Action	Command
Create changeset	pnpm changeset
Bump versions	pnpm changeset:version
Build + Publish	pnpm release

Workflows

1. Create Changeset

Create a .changeset/*.md file describing the change.

pnpm changeset

This is interactive. When automating, create the file directly:

# Generate a random changeset filename
CHANGESET_ID=$(node -e "console.log(Math.random().toString(36).slice(2,10))")

cat > .changeset/${CHANGESET_ID}.md << 'EOF'
---
"@superspec/cli": patch
---

<changeset summary here>
EOF

Bump type selection:

• patch: bug fixes, minor tweaks
• minor: new features, non-breaking changes
• major: breaking changes

2. Check Pending Changesets

List all pending changeset files (excluding config.json and README.md):

ls .changeset/*.md 2>/dev/null | grep -v README.md

If no files found → nothing pending, no version bump needed.

To view content:

for f in .changeset/*.md; do
  [[ "$(basename "$f")" == "README.md" ]] && continue
  echo "=== $f ==="
  cat "$f"
  echo
done

3. Version Bump

Consume pending changesets and update package versions + CHANGELOG:

pnpm changeset:version

This will:

• Read all pending .changeset/*.md files
• Update package.json version fields
• Update/create CHANGELOG.md in each affected package
• Delete consumed changeset files

After version bump, review changes:

git diff packages/*/package.json packages/*/CHANGELOG.md

4. Publish to npm

Build all packages and publish to npm registry: