Claude Code Plugin Release
Skill ActiveAutomated 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.
To streamline and automate the complex process of releasing new versions of Claude Code plugins, ensuring consistency and reducing manual errors.
Features
- Automated version increments across multiple manifests
- NPM publishing for `npx` compatibility
- Git tagging and GitHub release creation
- Changelog generation and commit updates
- Build verification and sync operations
Use Cases
- Automating patch, minor, or major version updates for Claude Code plugins.
- Ensuring consistent versioning across `package.json`, `marketplace.json`, and `plugin.json`.
- Simplifying the process of publishing new plugin versions to npm and GitHub.
- Generating release notes and updating changelogs automatically.
Non-Goals
- Developing or testing the plugin's core functionality.
- Managing plugin dependencies beyond version syncing.
- Automating the entire CI/CD pipeline for a plugin.
- Manually reviewing code changes before a release.
Documentation
- info:Configuration & parameter referenceThe SKILL.md mentions configuration via environment variables and a settings file, but specific parameters and their default values are not explicitly documented.
Code Execution
- info:ValidationWhile Git commands and npm scripts are used, there's no explicit mention or evidence of a schema library for validating input arguments or structured output beyond what npm/git provide.
Security
- warning:Unguarded Destructive OperationsThe workflow includes `npm publish`, `git push`, and `git tag`, which are destructive/mutating operations. While a confirmation is implied by the manual steps, there isn't an explicit 'dry-run' or explicit per-step confirmation mechanism documented.
Scope
- warning:Dry-run previewWhile the SKILL.md details manual steps for Git and npm operations, there is no explicit `--dry-run` flag or equivalent preview mechanism documented for the release process itself, which involves destructive operations like publishing and pushing.
Installation
npx skills add thedotmack/claude-memRuns the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.
Quality Score
Trust Signals
Similar Extensions
Rule Effectiveness Analysis
100Analyze which rules are actively used vs inert. Detect coverage gaps. Recommend pruning to reduce token consumption.
Release Manager
100Use when the user asks to plan releases, manage changelogs, coordinate deployments, create release branches, or automate versioning.
Releasing Clickup Cli
100Publishes a new version of clickup-cli to npm, updates Homebrew tap, writes release notes, and syncs the agent skill. Use when releasing a new version, bumping version, or verifying a release.
Secrets Management
100Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
ClawSweeper Skill
100Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, commit-review reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions monitoring, permissions, gates, and manual backfills.
Azure Deploy
100Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.