Skill

claude-code-plugin-release

Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.

Node

Git

Github

git-workflow

deployment

npx claudepluginhub alamator/claude-memory --plugin claude-mem

Tool Access

This skill uses the workspace's default tool permissions.

Preview

**IMPORTANT:** You must first plan and write detailed release notes before starting the version bump workflow.

Supporting Assets

scripts/generate_changelog.js

SKILL.md

Similar Skills

claude-code-plugin-release

72.5k

Automates semantic versioning and release for Claude Code plugins: increments versions in package.json/marketplace.json/plugin.json, npm publishes, verifies builds, git tags, creates GitHub releases, generates changelogs.

1 file

claude-mem

version-bumper

1.9k

Automates semver bumps for Claude Code plugins: updates plugin.json and marketplace.extended.json, regenerates marketplace.json, verifies consistency, preps git tags.

10 files5 tools

jeremy-plugin-tool

Release Claude Code Plugin

Releases Claude Code plugins by merging version branches to main, running npm/pytest tests, tagging with git, updating CHANGELOG.md, and creating next version branches. Use after plugin development on 'release' or 'publish'.

cat

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 4, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Version Bump & Release Workflow

IMPORTANT: You must first plan and write detailed release notes before starting the version bump workflow.

CRITICAL: ALWAYS commit EVERYTHING (including build artifacts). At the end of this workflow, NOTHING should be left uncommitted or unpushed. Run git status at the end to verify.

Preparation

Analyze: Determine if the change is a PATCH (bug fixes), MINOR (features), or MAJOR (breaking) update.

Environment: Identify the repository owner and name (e.g., from git remote -v).

Paths: Verify existence of package.json, .claude-plugin/marketplace.json, and plugin/.claude-plugin/plugin.json.

Workflow

Update: Increment version strings in all configuration files.

Verify: Use grep to ensure all files match the new version.

Build: Run npm run build to generate fresh artifacts.

Commit: Stage all changes including artifacts: git add -A && git commit -m "chore: bump version to X.Y.Z".

Tag: Create an annotated tag: git tag -a vX.Y.Z -m "Version X.Y.Z".

Push: git push origin main && git push origin vX.Y.Z.

Release: gh release create vX.Y.Z --title "vX.Y.Z" --notes "RELEASE_NOTES".

Changelog: Regenerate CHANGELOG.md using the GitHub API and the provided script:

gh api repos/{owner}/{repo}/releases --paginate | ./scripts/generate_changelog.js > CHANGELOG.md

Sync: Commit and push the updated CHANGELOG.md.

Notify: Run npm run discord:notify vX.Y.Z if applicable.

Finalize: Run git status to ensure a clean working tree.

Checklist

All config files have matching versions

npm run build succeeded

Git tag created and pushed

GitHub release created with notes

CHANGELOG.md updated and pushed

git status shows clean tree