skills.rest
verkyyi
verkyyiCOMMUNITY
Explore all skills by this author →
Website𝕏@verkyyiGitHub

release-plugin

Bump plugin.json, sync README, and create a GitHub Release with commit changelog.

6|Updated Feb 15, 2026
Search Tags:#automation#git#versioning#github#plugin#release#claude-code
One-click install
npx skills add https://github.com/verkyyi/always-on-claude --skill release-plugin-verkyyi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-plugin
Source: https://github.com/verkyyi/always-on-claude/tree/main/scripts/runtime/codex-home/skills/release-plugin
Command: npx skills add https://github.com/verkyyi/always-on-claude --skill release-plugin-verkyyi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cut a new semver-tagged release of a Claude Code plugin in the current working directory by bumping plugin.json, syncing README references, and publishing a GitHub Release with a changelog derived from commits since the last tag.

Core Features & Use Cases

  • Bump the plugin version in .claude-plugin/plugin.json to a new semantic version.
  • Update README sections to reflect the new release version for consistency with marketplaces.
  • Create and publish a GitHub Release with notes summarizing commits since the previous tag, and push tags to the repository.
  • Preconditions and fallback handling ensure proper gating when there are no new commits or tags are missing.

Quick Start

From your plugin repository, run the release-plugin to cut and publish a new version.

Frequently Asked Questions about release-plugin

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

FAQPage Schema
How do I automate version bumping and GitHub release for a Claude Code plugin?▼

To automate GitHub release for a Claude Code plugin, run the release plugin to bump the semver version in plugin.json, sync README references, and publish a GitHub Release with commit-derived changelog notes.

What prerequisites are needed to publish a Claude Code plugin release?▼

Publishing a Claude Code plugin release requires a clean git working tree on the main branch, a plugin.json file with a version field, and gh CLI authentication configured with repository scope.

How does a semver-tagged release generate its changelog from git commits?▼

A semver-tagged release generates its changelog by summarizing git commits between the newly created tag and the previous tag, then automatically including these notes in the published GitHub Release.

Can I use this release automation if my git working tree has uncommitted changes?▼

No, release automation requires a clean git working tree on the main branch to ensure version bumping, README alignment, and commit tagging operate without conflicts or lost modifications.

What happens if there are no new commits since the last plugin release tag?▼

If no new commits exist since the last tag, the release process applies precondition gating and fallback handling to stop execution, preventing duplicate empty GitHub releases.

Does the release process update README sections to match the new plugin version?▼

Yes, the release process updates README sections to reflect the new version, ensuring documentation stays aligned with plugin marketplaces after the plugin.json version bump.

Related Skills

Explore More Software Engineering Skills→
Trystan-SATrystan-SA
4

postkit-release

Bump the version, create a GitHub Release, and publish postkit to npm.

Community
Advanced
ayubunayubun
8

maintaining-a-marketplace

Maintain opencode Plugin Marketplace consistency across plugin.json, marketplace.json, and CHANGELOG.md.

Community
Intermediate
gtappsgtapps
69

release

Automate plugin release workflows with semver bumps, changelog updates, and GitHub releases.

Community
Advanced
autonomy-cloudautonomy-cloud
2

release

Dispatch a GitHub Actions Release workflow with a validated semantic version bump.

Official
Intermediate