release

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

69|12|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/gtapps/claude-code-hermit --skill release-gtapps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/gtapps/claude-code-hermit/tree/main/plugins/claude-code-dev-hermit/.claude/skills/release
Command: npx skills add https://github.com/gtapps/claude-code-hermit --skill release-gtapps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cut a release for claude-code-dev-hermit — bumps semver in plugin.json, marketplace.json, and the README badge, writes a CHANGELOG entry, commits, tags, pushes, and creates a GitHub release. Use whenever releasing a new version of claude-code-dev-hermit.

Core Features & Use Cases

  • Automatically bumps version in plugin.json, marketplace.json, and the README badge.
  • Writes a CHANGELOG entry and commits, tags, and pushes the changes.
  • Creates a GitHub release with release notes derived from the changelog.

Quick Start

Run the release workflow to bump the version, update changelog, commit, tag, push, and create a GitHub release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate plugin releases with semver bumps and GitHub releases?

Automating plugin releases involves bumping the semver version across plugin.json, marketplace.json, and README badges, then committing, tagging, and pushing changes to create a GitHub release with generated changelog notes.

What is the process for updating a changelog during a continuous delivery release?

Updating a changelog during a continuous delivery release requires writing a new entry reflecting version changes, committing the update alongside version bumps, and using the changelog content to generate the final GitHub release notes.

Do I need to manually update marketplace.json when releasing a new plugin version?

No, you do not need to manually update marketplace.json. The release workflow automatically enforces semver bumps across marketplace.json, plugin.json, and the README badge to ensure version consistency.

How do annotated git tags work when cutting a plugin release?

Annotated git tags mark specific commits during a plugin release. The workflow creates these tags after committing version bumps and changelog updates, then pushes them to trigger the corresponding GitHub release.

What's the best way to manage version bumps across multiple plugin files?

The best way to manage version bumps across multiple plugin files is using an automated release workflow that enforces semver consistency across plugin.json, marketplace.json, and README badges simultaneously.

Can I use this release workflow for repositories outside of claude-code-dev-hermit?

This specific release workflow is designed to cut releases for claude-code-dev-hermit. It targets that plugin's repository structure, enforcing semver and changelog updates specific to that project.