claude-code-plugin-release
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, npm publishing (so `npx claude-mem@X.Y.Z` resolves), build verification, git tagging, GitHub releases, and changelog generation.
- License 许可
- Apache-2.0
- 最近更新
- 2026-06-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- claude-code-plugin-release
- description
- Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, npm publishing (so `npx claude-mem@X.Y.Z` resolves), build verification, git tagging, GitHub releases, and changelog generation.
02 资源文件 1
03 SKILL.md 正文
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
-
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 claude-mem@X.Y.Zresolves from this)plugin/package.json— bundled plugin runtime deps.claude-plugin/marketplace.json— version insideplugins[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 manifestopenclaw/openclaw.plugin.json— OpenClaw plugin manifest
Verify coverage before editing:
git grep -l "\"version\": \"<OLD>\""should list all seven. If a new manifest has been added since this doc was last updated, update this list.
Workflow
- Update: Increment the version string in every path above. Do NOT touch
CHANGELOG.md— it's regenerated. - Verify:
git grep -n "\"version\": \"<NEW>\""— confirm all seven files match.git grep -n "\"version\": \"<OLD>\""— should return zero hits. - Build and sync:
npm run build-and-syncto regenerate artifacts, sync the local marketplace copy, restart the worker, and clear the queue. Do not use plainnpm run buildfor release validation because it can leave the local marketplace/worker out of sync. - Commit:
git add -A && git commit -m "chore: bump version to X.Y.Z". - Tag:
git tag -a vX.Y.Z -m "Version X.Y.Z". - Push:
git push origin main && git push origin vX.Y.Z. - Publish to npm (this is what makes
npx claude-mem@X.Y.Zwork):
Thenpm publishprepublishOnlyscript re-runs the package build automatically. After publish, runnpm run build-and-syncagain if the publish build touched local artifacts. Confirm publish succeeded:
Alternative:npm view claude-mem@X.Y.Z version # should print X.Y.Znpm run release:patch/release:minor/release:majorinvokesnpand handles tag+push+publish in one shot — use ONLY if you skipped steps 4–6, otherwisenpwill error on the existing tag. - GitHub release:
gh release create vX.Y.Z --title "vX.Y.Z" --notes "RELEASE_NOTES". - Changelog: Regenerate via the project's changelog script:
(Runsnpm run changelog:generatenode scripts/generate-changelog.js, which pulls releases from the GitHub API and rewritesCHANGELOG.md.) - Sync changelog: Commit and push the updated
CHANGELOG.md. - Notify: Run the Discord notification from
~/Scripts/claude-mem/, where the.envwith Discord webhook details lives:
Do this even when the release worktree does not have a localcd ~/Scripts/claude-mem/ && npm run discord:notify vX.Y.Z.env. - Finalize:
git status— working tree must be clean.
Checklist
- [ ] All seven config files have matching versions
- [ ]
git grepfor old version returns zero hits - [ ]
npm run build-and-syncsucceeded - [ ] Git tag created and pushed
- [ ]
npm publishsucceeded andnpm view claude-mem@X.Y.Z versionconfirms it (sonpx claude-mem@X.Y.Zresolves) - [ ] GitHub release created with notes
- [ ]
CHANGELOG.mdupdated and pushed - [ ] Discord notification run from
~/Scripts/claude-mem/ - [ ]
git statusshows clean tree
04 同仓库更多 Skills
wowerpoint
Turn one document into a kawaii NotebookLM slide-deck PDF. Use for "wowerpoint this", "make a deck about <file>", "turn this report into slides", or any request to render a single document as shareable narrative slides.
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests", "week-by-week story", "serial timeline", or "narrative chapters" of a project's history.
timeline-report
Generate a "Journey Into [Project]" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.
standup
Convene the recently-active git worktrees as named agents in a markdown group chat, have them reconcile what each changed, and converge on ONE consolidated worktree. Each branch is an agent that posts to a shared STANDUP.md (YAML front matter holds the GOAL + PROMPT; the body is the chat log), then the room agrees on a merge order and a single consolidation plan in the SUMMATION. The room is filled either by time window (past 1h / 4h / 24h / 7d / all — only worktrees active in it join, so a 40-worktree machine collapses to the handful you actually touched) or by hand-picking specific worktrees and/or open GitHub PRs from a checkbox-style list. Use this skill whenever the user says "standup", "run the standup", "reconcile my worktrees", "consolidate worktrees", "merge these branches together", "merge these PRs", "combine these worktrees and pull requests", "what's everyone at", "have my worktrees check in", or wants several branch-named agents to coordinate / resolve overlapping work into one deliverable through a shared chat file — even if they don't say the word "standup".
smart-explore
Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.
pathfinder
Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.