メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Meta knowledge for creating Claude skills. Provides templates, best practices, and patterns for building effective skills with routing tables and reference files. Load this when creating new skills or understanding the skill system. Triggers: create skill, new skill, skill template, skill architecture, SKILL.md.
Index of Mechanic documentation with summaries and links. Load this to understand what documentation exists and where to find detailed information on specific topics. Triggers: docs, documentation, reference, guide, help.
Context for the Mechanic/Fen WoW addon development ecosystem. Covers all components (Mechanic, FenCore, FenUI, MechanicLib), their relationships, and AFD principles. Load this at the start of addon work. Triggers: ecosystem, fen, fencore, fenui, mechanic, addon, context.
Context for FenCore - the pure logic library for WoW addons. Covers utility functions, math helpers, table operations, and environment detection. Load this when working with FenCore or needing utility functions. Triggers: fencore, utility, math, table, logic, pure functions.
Context for FenUI - the UI widget library for WoW addons. Covers frames, layouts, buttons, panels, and theming. Load this when building addon UI or working with FenUI widgets. Triggers: fenui, ui, widget, frame, layout, panel, button, tabs.
Context for Mechanic - the WoW addon development hub. Covers the CLI, MCP server, dashboard, in-game modules, and MechanicLib. Load this for deep understanding of Mechanic tooling. Triggers: mechanic, mech, cli, mcp, dashboard, tools, development hub.
| name | s-release |
| description | 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. |
Expert guidance for the full addon release workflow using Mechanic automation.
MANDATORY: Always use CLI commands before manual exploration.
| Task | Command |
|---|---|
| Full Release | mech release MyAddon 1.2.0 "Release message" |
| Bump Version | mech call version.bump -i '{"addon": "MyAddon", "version": "1.2.0"}' |
| Add Changelog | mech call changelog.add -i '{"addon": "MyAddon", "version": "1.2.0", "message": "..."}' |
| Commit Changes | mech call git.commit -i '{"addon": "MyAddon", "message": "Release 1.2.0"}' |
| Create Tag | mech call git.tag -i '{"addon": "MyAddon", "version": "1.2.0"}' |
.toc filesCHANGELOG.md updates with categories| Request type | Load reference |
|---|---|
| Release workflow, changelog format | ../../docs/integration/release.md |
| CLI Reference | ../../docs/cli-reference.md |
# Recommended: Validates → Bumps → Changelogs → Commits → Tags
mech release MyAddon 1.2.0 "Added cooldown tracking and fixed memory leaks"
mech call addon.validate -i '{"addon": "MyAddon"}'mech call addon.lint -i '{"addon": "MyAddon"}'mech call addon.test -i '{"addon": "MyAddon"}'mech call addon.deprecations -i '{"addon": "MyAddon"}'### Added: New features### Changed: Changes to existing features### Fixed: Bug fixes### Removed: Removed features### Deprecated: Features to be removed### Security: Security-related changes