- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add thedotmack/claude-mem --skill version-bump -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add thedotmack/claude-mem --skill version-bump -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add thedotmack/claude-mem --skill version-bump -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add thedotmack/claude-mem --skill version-bump -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/thedotmack/claude-mem/tree/HEAD/plugin/skills/version-bump來自發布者
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.
Analyze: Determine if the change is PATCH (bug fixes), MINOR (features), or MAJOR (breaking).
Environment: Identify repository owner/name from git remote -v.
Paths — every file that carries the version string:
package.json — the npm/npx-published version (npx [email protected] 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 manifestplugin/.claude-plugin/plugin.json — bundled Claude-plugin manifest.codex-plugin/plugin.json — Codex-plugin manifestplugin/.codex-plugin/plugin.json — bundled Codex-plugin manifest.qoder-plugin/plugin.json — Qoder plugin manifestplugin/.qoder-plugin/plugin.json — bundled Qoder plugin manifestopenclaw/openclaw.plugin.json — OpenClaw plugin manifest.grok-plugin/plugin.json — Grok plugin manifestclaude-mem-cursor/.cursor-plugin/plugin.json — Cursor plugin manifestclaude-mem-grok-bot/.cursor-plugin/plugin.json — Grok Bot Cursor plugin manifestdsh/package.json — bundled DSH plugin packageREADME.md — the version badge (version-X.Y.Z-green), not a "version" keyVerify coverage before editing: git grep -l "\"version\": \"<OLD>\"" should list the fourteen JSON files above, and git grep -n "version-<OLD>-green" the README badge. If a new manifest has been added since this doc was last updated, update this list.
CHANGELOG.md — it's regenerated.git grep -n "\"version\": \"<NEW>\"" — confirm all fourteen JSON files match, and the README badge reads version-<NEW>-green. git grep -n "\"version\": \"<OLD>\"" — should return zero hits.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.git add -A && git commit -m "chore: bump version to X.Y.Z".git tag -a vX.Y.Z -m "Version X.Y.Z".git push origin main && git push origin vX.Y.Z.gh release create vX.Y.Z --title "vX.Y.Z" --notes "RELEASE_NOTES".npm run changelog:generate
(Runs node scripts/generate-changelog.js, which pulls releases from the GitHub API and rewrites CHANGELOG.md.)CHANGELOG.md.prepublishOnly rebuilds the package. If npm view [email protected] version
already resolves, skip the publish and continue with post-publish checks.claude-mem only, bypass 2FA)
in the maintainer's Mac ~/.npmrc; he issues a new one every month. It is
deliberately NOT in any backup (grok-bot-backups excludes secrets), so do
not go looking for it elsewhere. Publish from a clean worktree of the tag
(inside the project's .scratch/) so uncommitted edits never ship:
git worktree add --detach .scratch/release-X.Y.Z vX.Y.Z
cd .scratch/release-X.Y.Z && npm install --ignore-scripts
npm whoami # must print thedotmack; 401 = token expired
npm publish --access public # prepublishOnly rebuilds the package
Finish every other
step, then: open
for the maintainer (), replace the token value in with
, and so he can paste the new token
there. Never ask for the token in chat. Re-run , then publish.
Do not wait on — its secret
has failed every tag since v13.26.1 ().
The publish rebuild rewrites with minifier-name churn
only; discard it with the worktree ().git grep for old version returns zero hitsnpm run build-and-sync succeededCHANGELOG.md updated and pushednpm whoami succeeded and the agent ran npm publish --access publiclatest both verified after publishing~/Scripts/claude-mem/ only after npm verificationgit status shows clean treeAutomated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, Gi
---name: version-bumpdescription: Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across…---# plugin/skills/version-bump/SKILL.md總覽
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. Ends with the agent running npm publish itself using the maintainer's npm token.
常見問題
從發布者下載 plugin/skills/version-bump/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/thedotmack/claude-mem。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。
npm whoami fails, the monthly token has expired.open <url>~/.npmrcPASTE_NEW_TOKEN_HEREopen -e ~/.npmrcnpm whoami.github/workflows/npm-publish.ymlNPM_TOKENE404 ... PUT https://registry.npmjs.org/claude-memplugin/scripts/*.cjsgit worktree remove --forcenpm view [email protected] version
npm view claude-mem version
If the publish build touched tracked artifacts, run npm run build-and-sync,
review the result, and commit/push any legitimate changes. Then run the
Discord notification from ~/Scripts/claude-mem/, where the .env with
webhook details lives:
cd ~/Scripts/claude-mem/ && npm run discord:notify vX.Y.Z
Do this only after npm verification, and even when the release worktree does
not have a local .env.git status — working tree must be clean and everything must
be pushed.