Agent Skills › MMFoundation/WallpaperMachine › hotfix-release

hotfix-release

GitHub

执行紧急热修复发布流程，从最新标签切分支应用修复，运行CI门禁，经确认后推送并发布补丁版本。

.agents/skills/hotfix-release/SKILL.md MMFoundation/WallpaperMachine

Trigger Scenarios

请求紧急修复要求立即发布补丁

Install

npx skills add MMFoundation/WallpaperMachine --skill hotfix-release -g -y

More Options

Non-standard path

npx skills add https://github.com/MMFoundation/WallpaperMachine/tree/main/.agents/skills/hotfix-release -g -y

Use without installing

npx skills use MMFoundation/WallpaperMachine@hotfix-release

指定 Agent (Claude Code)

npx skills add MMFoundation/WallpaperMachine --skill hotfix-release -a claude-code -g -y

安装 repo 全部 skill

npx skills add MMFoundation/WallpaperMachine --all -g -y

预览 repo 内 skill

npx skills add MMFoundation/WallpaperMachine --list

SKILL.md

Frontmatter

{
    "name": "hotfix-release",
    "description": "Ship an urgent fix to users as its own patch release, without the unreleased work on main. Use when the developer asks for an emergency, urgent, hotfix or \"patch release right now\" fix (a broken sign-in or download, a crash on launch). Cuts a hotfix\/<x.y.z> branch from the newest release tag, puts only the fix on it with its test, runs the gate, and after the developer confirms pushes it with `release: patch`; CI then releases it and merges it back into main."
}

Emergency patch release

Follow Emergency patch release for someone else in docs/release.md, step by step; Hotfix releases above it says why each step is there. The rules in AGENTS.md outrank this skill, and it grants nothing beyond them.

The developer asking for the emergency release is the request a release: line needs. It is not permission to push: pushing the hotfix branch publishes the release to every user, so show what will ship and push only once the developer agrees. Never push to, squash or rebase main for a hotfix; CI merges it back.