skills.rest
devs6186
devs6186COMMUNITY
Explore all skills by this author →
GitHub

claude-code-plugin-release

Automate semantic versioning and release workflows for Claude Code plugins.

1|Updated Mar 19, 2026
Search Tags:#automation#git#changelog#versioning#npm#github#release-workflow
One-click install
npx skills add https://github.com/devs6186/claude-private-skills-agents-commands --skill claude-code-plugin-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-code-plugin-release
Source: https://github.com/devs6186/claude-private-skills-agents-commands/tree/main/skills/claude-code-plugin-release
Command: npx skills add https://github.com/devs6186/claude-private-skills-agents-commands --skill claude-code-plugin-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This workflow automates semantic versioning and release workflows for Claude Code plugins, coordinating version bumps across multiple config files and ensuring a reproducible release process.

Core Features & Use Cases

  • Automated version bumps across package.json, marketplace.json, and plugin.json
  • Build verification, git tagging, GitHub releases, and changelog generation
  • End-to-end release automation for plugin pipelines

Quick Start

Update your plugin repository and run the release workflow to publish a new version.

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 for Claude Code plugins across multiple config files?▼

Automating semantic versioning for Claude Code plugins coordinates version bumps across package.json, marketplace.json, and plugin.json. This ensures all configuration files remain synchronized during the release workflow, preventing version mismatch errors.

What does an end-to-end release workflow for npm and GitHub plugins include?▼

An end-to-end release workflow includes automated version bumps, npm build verification, git tagging, GitHub releases, and changelog generation. These steps ensure a clean, reproducible release process for your plugin repository.

Do I need the GitHub CLI to automate git tagging and GitHub releases for my plugin?▼

Yes, the release workflow requires the GitHub CLI to execute git and GitHub release steps. Proper changelog tooling and npm build capabilities are also necessary to ensure a clean, reproducible release.

How do I generate changelogs automatically during a plugin release?▼

Automatic changelog generation occurs during the release workflow by utilizing proper changelog tooling alongside version bumps and git tagging. This ensures release notes are captured accurately without manual intervention.

Can I use this release automation if my repository only has a package.json?▼

No, this workflow specifically applies to repositories containing package.json, marketplace.json, and plugin.json. All three configuration files must be present and updated to execute the coordinated version bump successfully.

Related Skills

Explore More Software Engineering Skills→
hiddink-aihiddink-ai
1

hiddink-harness:npm-version

Automate npm package version bumps, changelogs, and git tags.

Official
Intermediate
wipcomputerwipcomputer
3

wip-release

Automate software releases by bumping versions, updating changelogs, and publishing to npm and GitHub Packages.

Official
Advanced
bychrisrbychrisr

release

Coordinate software releases with changelog generation, canary verification, and npm publishing.

Community
Advanced
sergio-bershadskysergio-bershadsky
15

version

Bumps semantic plugin versions in manifests and catalogsGitHub via commits and tags.

Community
Intermediate