How do I install the Claude Code Plugin Release skill?

Run npx skillmds@latest add dqtx760/claude-code-plugin-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Claude Code Plugin Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claude Code Plugin Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Claude Code Plugin Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Claude Code Plugin Release?

dqtx760 (@dqtx760) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Claude Code Plugin Release by dqtx760

Name: Claude Code Plugin Release
Author: dqtx760

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.

dqtx760 3300f9c 2 files · 4.4 KB Updated Sep 17, 2026

File contents

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

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: npm run build to regenerate artifacts.
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.Z work):
```
npm publish
```
The prepublishOnly script re-runs npm run build automatically. 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.
GitHub release: gh release create vX.Y.Z --title "vX.Y.Z" --notes "RELEASE_NOTES".
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.)
Sync changelog: Commit and push the updated CHANGELOG.md.
Notify: npm run discord:notify vX.Y.Z if applicable.
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 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
git status shows clean tree

---name: claude-code-plugin-releasedescription: 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.---# 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.## Preparation1. **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.## Workflow1. **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**: `npm run build` to regenerate artifacts.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): ```bash npm publish ``` The `prepublishOnly` script re-runs `npm run build` automatically. Confirm publish succeeded: ```bash 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: ```bash 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**: `npm run discord:notify vX.Y.Z` if applicable.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` 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- [ ] `git status` shows clean tree

Frequently asked questions