claude-code-plugin-release

Automate semantic versioning and release operations for Claude Code plugins.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill claude-code-plugin-release-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-plugin-release
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/claude-mem/plugin/skills/version-bump
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill claude-code-plugin-release-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of error-prone, inconsistent release work for Claude Code plugins by automating semantic version bumps, builds, tagging, publishing, and release documentation.

Core Features & Use Cases

  • Automated semantic versioning: Updates versions across all plugin-related manifests and package files.
  • End-to-end release workflow: Runs build-and-sync validation, creates Git tags, publishes to npm, and generates GitHub releases.
  • Changelog and notification automation: Regenerates CHANGELOG.md and sends a Discord notification after release.

Quick Start

Use this Skill to release a new plugin version by following its version-bump workflow steps from analyzing the release type through publishing, tagging, changelog generation, and final verification.

Frequently Asked Questions about claude-code-plugin-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate semantic versioning and npm publishing for a Claude Code plugin?

Automate semantic versioning and npm publishing by incrementing version strings across all manifests, running build verification, creating Git tags, and publishing so npx resolves the intended version.

What is the best way to generate a changelog and GitHub release for a Claude Code plugin?

Generate a changelog and GitHub release by regenerating CHANGELOG.md, creating Git tags, and publishing to GitHub releases as part of an end-to-end automated workflow.

How do I ensure version consistency across package files before publishing a plugin?

Ensure version consistency by running strict version consistency checks via grep across all required manifests and package files before proceeding with the release.

Can I run a patch, minor, and major release cycle with automated git tagging?

Run patch, minor, and major release cycles with automated git tagging, build verification, and npm publishing to ensure deterministic and reliable plugin releases.

Why does npx resolve the wrong version after publishing my plugin?

npx may resolve the wrong version if build-and-sync is not deterministic or if version strings are not strictly consistent across all package files; strict checks via grep resolve this.