agentskills.codes
SR

s-release

by FalkiconCodingSource

Automates the release cycle for WoW Addons, handling versioning and changelog management.

DeploymentAutomation

Install

mkdir -p .claude/skills/s-release && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12243" && unzip -o skill.zip -d .claude/skills/s-release && rm skill.zip

Installs to .claude/skills/s-release

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Prepare and execute an addon release, including version bumping, changelog updates, git tagging, and validation. Use when ready to publish a new version. Triggers: release, version bump, changelog, git tag, publish.
215 chars✓ has a “when” trigger
Beginner

Key capabilities

  • →Automate the full release workflow for an addon, including version bumping, changelog updates, git tagging, and validation.
  • →Manage consistent version bumping across .toc files.
  • →Maintain structured CHANGELOG.md updates with categories.
  • →Integrate with Git for automated commits and annotated tags.

How it works

The skill executes a sequence of commands: validates, bumps the version, updates the changelog, commits changes, and creates a git tag. This automates the release process for WoW addons.

Inputs & outputs

You give it
An addon name, version number, and a release message
You get back
A released addon with updated version, changelog, and git tags

When to use s-release

  • →Releasing a new version
  • →Bumping version number
  • →Updating addon changelogs

About this skill

Releasing WoW Addons

Guidance for the release workflow with Mechanic. A release changes files, creates a commit and a tag: never run it without an explicit request from the user, and always preview first.

Related Commands

MCP Tools

Call MCP tools directly (using-mechanic). Inputs are in the generated command reference.

TaskMCP Tool
Validate TOC and structureaddon.validate(addon="MyAddon")
Lint / tests / deprecationsaddon.lint, addon.test or sandbox.test, addon.deprecations (limited database, see s-audit)
Preview the releaserelease.all(addon, version, message, category, dry_run=true)
Run the releaserelease.all(addon, version, message, category) after the user confirms
Individual steps (recovery only)version.bump, changelog.add, git.commit, git.tag

Workflow

  1. Pre-release checks: addon.validate, addon.lint, tests, addon.deprecations. Fix or report problems.
  2. Dry run: release.all with dry_run: true. It runs the same preflight (tag conflict check, existing staged changes) and returns steps_planned with nothing changed. Show the planned version, changelog text, category and tag to the user.
  3. Ask for confirmation of exactly that plan. Do not proceed on silence.
  4. Run release.all without dry_run. It bumps the TOC version, inserts the changelog entry, commits only the addon's files (chore(release): v<version>), and creates the annotated tag v<version>.
  5. Report the version, commit hash and tag. Pushing and publishing are separate steps for the user.

Behaviour to know

  • Changelog categories: Added, Changed, Deprecated, Removed, Fixed, Security (case-insensitive; anything else fails with INVALID_CATEGORY). Default is Changed. The entry is inserted before the first existing ## [ heading, dated today.
  • Version: validated (INVALID_VERSION); the tag is v<version> and an existing tag is never moved (TAG_CONFLICT).
  • Preflight errors: STAGED_CHANGES (commit or unstage first), TAG_CONFLICT, NO_TOC, GIT_NOT_FOUND, PREFLIGHT_FAILED.
  • Not transactional: on failure the result is RELEASE_PARTIAL_FAILURE with details.failed_step, steps_completed and recovery. Completed steps are not rolled back, and rerunning release.all may duplicate the changelog entry. Inspect git status and git diff --cached, then finish the remaining steps individually.
  • A Mechanic release has two TOCs (!Mechanic and Mechanic) with separate versions and changelogs; release each addon by name and keep their changelogs in step.
  • The user's CLI equivalent is mech release ADDON VERSION MESSAGE --dry-run (cli-commands); agents use the MCP tool.

Routing Logic

Request typeLoad reference
Release workflow, changelog format../../../docs/integration/release.md
Human CLI reference../../../docs/cli-reference.md

When not to use it

  • →When manual exploration is preferred over CLI commands.
  • →When only validation, linting, testing, or auditing an addon is needed.

Limitations

  • →The skill is specific to releasing WoW addons.
  • →The skill requires using CLI commands for its operations.

How it compares

This skill automates the entire release workflow with a single command, unlike manually executing each step of version bumping, changelog updates, committing, and tagging.

Compared to similar skills

s-release side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
s-release (this skill)09moReviewBeginner
unity-editor-toolkit108moReviewAdvanced
workflow43moReviewIntermediate
setup-build-tools28moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

More by Falkicon

View all by Falkicon →

s-lint

Falkicon

>

00

k-docs

Falkicon

>

00

s-debug

Falkicon

>

00

k-fenui

Falkicon

>

00

s-audit

Falkicon

>

00

You might also like

unity-editor-toolkit

Dev-GOM

Automate and control Unity Editor with 500+ commands, real-time WebSocket communication, and SQLite integration for efficient game development.

10126

workflow

vercel

Creates durable, resumable workflows using Vercel's Workflow DevKit. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow devkit", or step-based orchestration.

431

setup-build-tools

aaddrick

Install build and extraction tools needed for building Claude Desktop Debian packages

212

macos-spm-app-packaging

Dimillian

Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project. Use when you need a from-scratch macOS app layout, SwiftPM targets/resources, a custom .app bundle assembly script, or signing/notarization/appcast steps outside Xcode.

17

railway-templates

davila7

Search and deploy services from Railway's template marketplace. Use when user wants to add a service from a template, find templates for a specific use case, or deploy tools like Ghost, Strapi, n8n, Minio, Uptime Kuma, etc. For databases (Postgres, Redis, MySQL, MongoDB), prefer the railway-database skill.

15

pinme

glitternetwork

This skill should be used when the user asks to "deploy", "upload", "publish", or "pin" any files, folders, frontend projects, or static websites to IPFS. Also activates when user mentions "pinme", "IPFS", or wants to share files via decentralized storage.

14

Search skills

Search the agent skills registry