s-release

Automate WoW addon release workflows with version bumps, changelog updates, git tagging, and validation.

16|5|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/Falkicon/Mechanic --skill s-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: s-release
Source: https://github.com/Falkicon/Mechanic/tree/main/.claude/skills/s-release
Command: npx skills add https://github.com/Falkicon/Mechanic --skill s-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare and execute the addon release process with minimal manual steps, reduce errors, and ensure consistent publishing of new versions.

Core Features & Use Cases

  • Version bumping, changelog updates, git tagging, and validation as a single, repeatable workflow.
  • Works across project repositories and CI pipelines to produce auditable release artifacts.
  • Use case: when ready to publish a new addon version, trigger a documented release sequence that updates version files, writes changelog entries, creates a git tag, and validates artifacts.

Quick Start

Run mech release MyAddon 1.2.0 to perform a full release workflow.

Frequently Asked Questions about s-release

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

FAQPage Schema
How do I automate WoW addon releases with version bumps and git tagging?

You can automate WoW addon releases by triggering a CLI-driven workflow that handles version bumps, updates changelog entries, creates git tags, and validates build artifacts in a single repeatable sequence.

What is the best way to update a changelog and create a git tag for a new addon version?

The best way to update a changelog and create a git tag is using an automated addon release workflow that formats changelog entries and applies git tags consistently during the version bump process.

Does this addon release automation work with CI pipelines?

Yes, the addon release automation works across project repositories and CI pipelines to produce auditable release artifacts through repeatable CLI-driven steps.

How do I validate build artifacts before publishing a new addon version?

You validate build artifacts by running an end-to-end release workflow that enforces CLI-driven validation steps immediately after updating version files and creating git tags.

Can I ensure repeatable and auditable publishing for World of Warcraft addon updates?

Yes, you can ensure repeatable and auditable publishing by executing a documented release sequence that automates version bumps, changelog formatting, and git tagging for every addon update.