Agent skill · software engineering · thedotmack
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer raised npm security.
Why this skill is useful
Adds an automated semantic versioning script that integrates with multiple manifest files and GitHub releases, which the AI cannot generate on its own.
What it needs
Requires gh, git, npm installed locally. Requires github account access. About 3k tokens when loaded. Last updated 2026-08-05. 89,894 stars on the source repository.
What this skill does
Version Bump & Release Workflow IMPORTANT: Plan and write detailed release notes before starting. CRITICAL: 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 1. Analyze: Determine if the change is PATCH (bug fixes), MINOR (features), or MAJOR (breaking). 2. Environment: Identify repository owner/name from git remote -v. 3. Paths — every file that carries the version string: package.json — the npm/npx-published version (npx claude-mem@X.Y.Z resolves from this) plugin/package.json — bundled plugin runtime deps .claude-plugin/marketplace.json — version inside plugins[0].version .claude-plugin/plugin.json — top-level Claude-plugin manifest plugin/.claude-plugin/plugin.json — bundled Claude-plugin manifest .codex-plugin/plugin.json — Codex-plugin manifest plugin/.codex-plugin/plugin.json — bundled Codex-plugin manifest openclaw/openclaw.plugin.json — OpenClaw plugin manifest Verify coverage before editing: git grep -l "\"version\": \"<OLD>\"" should list all eight. If a new manifest has been added since this doc was last updated, update this list. Workflow 1. Update: Increment the version string in every path above. Do NOT touch CHANGELOG.md — it's regenerated. 2. Verify: git grep -n "\"version\": \"<NEW>\"" — confirm all eight files match. git grep -n "\"version\": \"<OLD>\"" — should return zero hits. 3. Build and sync: npm run build-and-sync to regenerate artifacts, sync the local marketplace copy, restart the worker, and clear the queue. Do not use plain npm run build for release validation because it can leave the local marketplace/worker out of sync. 4. Commit: git add -A && git commit -m "chore: bump version to X.Y.Z". 5. Tag: git tag -a vX.Y.Z -m "Version X.Y.Z". 6. Push: git push origin main && git push origin vX.Y.Z. 7. GitHub release: gh release create vX.Y.Z --title "vX.Y.Z" --notes "RELEASENOTES". 8. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thedotmack/version-bump