菜单
Repair an already-published Gate release that has no assets by dispatching release-repair.yml without rewriting the historical release.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/minekube/gate --skill release-repair命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | release-repair |
| description | Repair an already-published Gate release that has no assets by dispatching release-repair.yml without rewriting the historical release. |
Releases already published with no assets are repaired by .github/workflows/release-repair.yml (manual dispatch from the default branch, contract pinned by release_repair_workflow_test.go). The two-job trust boundary is described in .github/CLAUDE.md.
It must live on the default branch and check the tag out, because workflow_dispatch compiles the workflow file at the dispatched ref - a repair input added to ci.yml would not exist on the old tags that need it. The build job pins Go via go-version-file: go.mod of the tag: today's Go is not a neutral substitute for an old tag's, e.g. go vet ./... on v0.48.0 is clean at go1.24.1 and reports two printf diagnostics at go1.26.2, which make test would surface as a false red on source that shipped fine. GoReleaser runs with --skip=publish (assets are uploaded separately with gh release upload --clobber) so a repair never rewrites a historical release's notes or identity - older tags (v0.63.0 and back) predate release: mode: keep-existing and would otherwise be deleted and recreated. Tags whose .goreleaser.yml predates version: 2 (v0.41.1 and older) cannot be repaired by a v2 toolchain; that is a finding to report, not a thing to work around.
