claude-code-plugin-release

Engineering Community

Repo stars 80,444
Author repo claude-mem

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, mark…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Preparation”, “Workflow”, “Checklist”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name claude-code-plugin-release directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Preparation / Workflow / Checklist” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / env-read; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Engineering
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @thedotmack · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: macOS · Linux · Windows
Runtime requirements: Node.js
Detected file/system behavior: Read-only
Write / modify
Env read
Detected network behavior: External requests
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview claude-code-plugin-release.preview

The current SKILL.md does not define a fixed output example.

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

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Preparation → Workflow → Checklist
terms    -> IMPORTANT · CRITICAL · Analyze · PATCH · MINOR · MAJOR · Environment · Paths — every file that carries the version string
files/cmd -> git status · git remote -v · package.json · npx claude-mem@X.Y.Z · plugin/package.json · .claude-plugin/marketplace.json · plugins[0].version · .claude-plugin/plugin.json
body sha256 -> 2b247c0ae048