claude-code-plugin-release

Automate semantic versioning and release workflows for Claude Code plugins.

Updated Jun 14, 2026
One-click install
npx skills add https://github.com/trehansalil/claude-mem-deploy --skill claude-code-plugin-release-trehansalil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-plugin-release
Source: https://github.com/trehansalil/claude-mem-deploy/tree/main/image/plugin/skills/version-bump
Command: npx skills add https://github.com/trehansalil/claude-mem-deploy --skill claude-code-plugin-release-trehansalil

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, git, github-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of semantic versioning and release management for Claude Code plugins, streamlining the workflow from version increment to GitHub release.

Core Features & Use Cases

  • Automated Versioning: Handles version increments across various plugin manifests.
  • NPM Publishing: Ensures npx [email protected] resolves correctly.
  • Build Verification: Validates the build artifacts before release.
  • Git Tagging and GitHub Releases: Automates git tagging and creation of GitHub releases.
  • Changelog Generation: Generates changelogs from release notes.

Quick Start

Run the version bump and release workflow for the 'claude-code-plugin' to update its version and publish a new release.

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 Claude Code plugins?

You can automate semantic versioning and npm publishing for Claude Code plugins by running a release workflow that increments version numbers in plugin manifests and publishes to the npm registry. This ensures the npx command resolves to the correct version.

How does automated changelog generation work from git tags and GitHub releases?

Automated changelog generation works by extracting release notes associated with git tags and GitHub releases, compiling them into a structured changelog. This process is triggered automatically as part of the release workflow after version incrementing.

Do I need npm and git installed to use this release management workflow?

Yes, you need npm and git installed locally, along with configured GitHub API access, to use this release management workflow. These dependencies are required for version incrementing, publishing packages, creating git tags, and generating GitHub releases.

What is the best way to handle git tagging and GitHub release creation for plugin updates?

The best way to handle git tagging and GitHub release creation for plugin updates is through an automated release workflow that validates build artifacts first, then applies the git tag and creates the corresponding GitHub release with generated changelogs.

Can I validate build artifacts before publishing a new plugin version to npm?

Yes, you can validate build artifacts before publishing a new plugin version to npm. The release workflow includes a build verification step that checks artifacts prior to executing the version increment and npm publishing processes.