release

Automate plugin releases by bumping versions, tagging commits, and publishing GitHub releases.

19|3|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/changoo89/claude-pilot --skill release-changoo89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/changoo89/claude-pilot/tree/main/.claude/skills/release
Command: npx skills add https://github.com/changoo89/claude-pilot --skill release-changoo89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repetitive plugin release processes are error-prone and time-consuming, requiring manual coordination of version bumps, changelogs, and releases across multiple manifests and platforms.

Core Features & Use Cases

  • Auto-bumps: update plugin.json and marketplace.json to keep versions in sync.
  • CHANGELOG automation: generate concise release notes from conventional commits.
  • Git operations: create and push tags, ensuring reproducible release state.
  • GitHub release: optional publishing of releases with notes.
  • Pre-flight validation: verify environment and manifests before releasing.

Quick Start

Run /999_release to perform a patch release and let CI/CD manage changelog generation and publishing.

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 versioning and tags?

You can automate plugin releases by running the release workflow to bump versions, tag commits, and publish GitHub releases. It synchronizes plugin.json and marketplace.json manifests while generating changelogs from conventional commits.

How do I generate a changelog from conventional commits for a GitHub release?

Generating a changelog from conventional commits is handled automatically during the release process. The workflow parses your commit history to create concise release notes for the GitHub release.

How do I keep plugin.json and marketplace.json versions in sync during a release?

Keeping plugin.json and marketplace.json versions in sync is achieved through atomic version updates. The release workflow automatically applies the version bump across both manifest files simultaneously.

Can I perform pre-flight validation before bumping versions and creating git tags?

Pre-flight validation is supported before bumping versions and creating git tags. The workflow verifies your environment and manifests to ensure a reproducible release state before applying changes.

What is the best way to handle patch, minor, and major version bumps for plugin releases?

Handling patch, minor, and major version bumps is managed by the release workflow. It applies the correct semantic version increment across your manifests and creates the corresponding git tag.

Do I need standard CLI tools to publish GitHub releases with this automation approach?

Standard CLI tools are required for optional GitHub release publishing. The workflow leverages them to create releases with your generated notes after validating manifests and pushing tags.