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 (so `npx claude-mem@X.Y.Z` resolves) is handed off to the human maintainer, who raised npm security.
Profile →npx skills add thedotmack/claude-mem --skill version-bump --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 h
- Preparation
- Workflow
- Checklist
npm publish # run by the HUMAN — the prepublishOnly script rebuilds the package npm view claude-mem@X.Y.Z version # should print X.Y.Z npm run changelog:generate cd ~/Scripts/claude-mem/ && npm run discord:notify vX.Y.Z
What does the version-bump skill do?
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 (so `npx claude-mem@X.Y.Z` resolves) is handed off to the human maintainer, who raised npm security.
How do I install it?
Run `npx skills add thedotmack/claude-mem --skill version-bump --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From thedotmack/claude-mem, a repository with 89,517 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.