AGENT SKILL

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
所属仓库
Army161/claude-mem
最近更新
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

  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
    • openclaw/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

  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 seven 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. Publish to npm (this is what makes npx claude-mem@X.Y.Z work):
    npm publish
    
    The prepublishOnly script re-runs the package build automatically. After publish, run npm run build-and-sync again if the publish build touched local artifacts. Confirm publish succeeded:
    npm view claude-mem@X.Y.Z version   # should print X.Y.Z
    
    Alternative: npm run release:patch / release:minor / release:major invokes np and handles tag+push+publish in one shot — use ONLY if you skipped steps 4–6, otherwise np will error on the existing tag.
  8. GitHub release: gh release create vX.Y.Z --title "vX.Y.Z" --notes "RELEASE_NOTES".
  9. Changelog: Regenerate via the project's changelog script:
    npm run changelog:generate
    
    (Runs node scripts/generate-changelog.js, which pulls releases from the GitHub API and rewrites CHANGELOG.md.)
  10. Sync changelog: Commit and push the updated CHANGELOG.md.
  11. Notify: Run the Discord notification from ~/Scripts/claude-mem/, where the .env with Discord webhook details lives:
    cd ~/Scripts/claude-mem/ && npm run discord:notify vX.Y.Z
    
    Do this even when the release worktree does not have a local .env.
  12. Finalize: git status — working tree must be clean.

Checklist

  • [ ] All seven config files have matching versions
  • [ ] git grep for old version returns zero hits
  • [ ] npm run build-and-sync succeeded
  • [ ] Git tag created and pushed
  • [ ] npm publish succeeded and npm view claude-mem@X.Y.Z version confirms it (so npx claude-mem@X.Y.Z resolves)
  • [ ] GitHub release created with notes
  • [ ] CHANGELOG.md updated and pushed
  • [ ] Discord notification run from ~/Scripts/claude-mem/
  • [ ] git status shows clean tree

04 同仓库更多 Skills

Army161
Army161/claude-mem

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.

★ 0
Army161
Army161/claude-mem

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.

★ 0
Army161
Army161/claude-mem

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.

★ 0
Army161
Army161/claude-mem

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".

★ 0
Army161
Army161/claude-mem

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.

★ 0
Army161
Army161/claude-mem

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.

★ 0