release

Automate addon releases to CurseForge and GitHub with semantic versioning.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mckalexee/ruby-slippers --skill release-mckalexee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/mckalexee/ruby-slippers/tree/main/.claude/skills/release
Command: npx skills add https://github.com/mckalexee/ruby-slippers --skill release-mckalexee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes the release process for a World of Warcraft addon by guiding users through pre-flight checks, changelog management, and version tagging.

Core Features & Use Cases

  • Pre-flight verification: ensure a clean working tree, correct branch, and up-to-date changelog.
  • Changelog & versioning: migrate the Unreleased section to a new version heading and generate release notes for distribution.
  • Release execution: commit changes, create a version tag, and push to GitHub and CurseForge with safeguards.

Quick Start

Run this procedure after updating CHANGELOG.md and setting the next version number.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate addon releases to CurseForge and GitHub?▼

Automate addon releases to CurseForge and GitHub by running a procedure that guides pre-flight checks, changelog updates, semantic version tagging, and pushing to both platforms to standardize the publishing workflow.

What pre-flight checks are needed before publishing a World of Warcraft addon release?▼

Pre-flight checks for publishing an addon release require ensuring a clean working tree, verifying the correct branch, and validating the version number against the changelog to prevent publishing errors.

How does changelog migration work for semantic versioning releases?▼

Changelog migration for semantic versioning moves the Unreleased section in CHANGELOG.md to a new version heading, generating proper release notes for distribution before committing and tagging the release.

Can I push a release to CurseForge without a clean working tree?▼

You cannot push a release to CurseForge without a clean working tree. The release execution requires validated version numbers and proper release notes migration to ensure safe publishing.

Do I need to manually update CHANGELOG.md before running addon release automation?▼

You need to update CHANGELOG.md and set the next version number before running the release automation. The procedure then migrates these changes into a new version heading for the final publish.