Release Claude Code Plugin

Orchestrate Claude Code plugin releases by synchronizing changelogs, version files, and git tags.

101|2|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/cowwoc/cat --skill release-claude-code-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Release Claude Code Plugin
Source: https://github.com/cowwoc/cat/tree/main/plugin/skills/release-plugin
Command: npx skills add https://github.com/cowwoc/cat --skill release-claude-code-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates a safe, auditable release of a Claude Code plugin by synchronizing changelogs, version files, and git tags.

Core Features & Use Cases

  • Release orchestration from version-branch validation through main merge, tag creation, and preparation of the next version branch.
  • Automatic alignment of CHANGELOG.md, package.json, .claude-plugin/plugin.json, and migrations/registry.json to ensure a clean, trackable release.
  • Use case: When a plugin version is ready for distribution, trigger the release workflow to publish the version with proper history and migration scaffolding.

Quick Start

Confirm your current branch is the release version branch, ensure all changes are committed, and follow the release sequence: tests, version validation, changelog update, merge to main, tag creation, next-version branch setup, migration script creation, registry update, commit, and push.

Frequently Asked Questions about Release Claude Code Plugin

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

FAQPage Schema
How do I safely release a Claude Code plugin and synchronize git tags with changelogs?

To safely release a Claude Code plugin, you orchestrate version-branch validation, align CHANGELOG.md with package.json and plugin.json, merge to main, create git tags, and scaffold the next version branch. This synchronizes changelogs, version files, and git tags for an auditable release.

What is the step by step process for Claude Code plugin versioning and migration?

The plugin versioning process involves running tests, validating versions, updating the changelog, merging to main, creating a tag, setting up the next-version branch, creating migration scripts, updating the registry, and pushing. This ensures trackable releases and proper migration scaffolding.

Do I need a specific branch structure to automate Claude Code plugin releases?

Yes, you need to confirm your current branch is the dedicated release version branch and ensure all changes are committed before starting. The release sequence validates this branch structure before proceeding to main merge and tag creation.

How does migration registry synchronization work during a plugin release?

Migration registry synchronization works by automatically aligning migrations/registry.json alongside package.json and .claude-plugin/plugin.json. It scaffolds migration scripts during the next-version branch setup to ensure a clean, trackable release history.

What are the limitations of manually managing git tags and changelogs for Claude Code plugins?

Manually managing git tags and changelogs risks misaligned versions across package.json, plugin.json, and registry.json. Without enforced prerequisites and branch validation, you may push incomplete migration scripts or skip required test and documentation updates.