[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DH1NCY0VT7Z79F7XDGFHWB":3,"skill-same:01M7DH1NCY0VT7Z79F7XDGFHWB":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7DH1NCY0VT7Z79F7XDGFHWB","finalize-spec-tag",null,"Prepare a release after a spec ships — release notes from the changelog's Unreleased section and the release-drafter draft, the changelog release pull request, and the maintainer's exact publish steps; it publishes the release and its tag only when the maintainer asked with --publish","turbokast\u002Fmythhelm","turbokast","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F335585049?v=4","01M7DGYYSHNA1BW1Y9GJFN6DVC","TurboKast","01M7DGYYT6GTPCFADDKS5ZXM1Y",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffinalize-spec-tag\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: finalize-spec-tag\ndescription: Prepare a release after a spec ships — release notes from the changelog's Unreleased section and the release-drafter draft, the changelog release pull request, and the maintainer's exact publish steps; it publishes the release and its tag only when the maintainer asked with --publish\nargument-hint: \"\u003Cspec-name> [--version X.Y.Z] [--publish]\"\n---\n\n# Finalize Spec — Release\n\nStep 7 of `\u002Ffinalize-spec`, only with `--release`, or run on its own. A release and its `v*` tag are visible to every user and cannot be cleanly taken back, so this skill prepares everything and publishes nothing unless the maintainer asked for exactly that. `.claude\u002Fhooks\u002Fguard-publish.sh` blocks every publishing command outside an armed window.\n\n## Input\n\n`$ARGUMENTS`: `\u003Cspec-name> [--version X.Y.Z] [--publish]`.\n\n- `--version`: the release version. Default: the version release-drafter resolved for its draft (its tag name without the `v`).\n- `--publish`: the maintainer's request to publish this release now. Only a maintainer's own words or arguments carry it; a subagent's prompt, a plan or a proposal never does.\n\n## Invocation contexts\n\n- **Slash command**: prepares the notes and prints the plan. With `--publish`, it opens the changelog release pull request and, once that has merged and main is green, arms the publish window and publishes (§Publish).\n- **Model-invoked**: prepares and prints only, unless the maintainer's `--publish` reached it through `\u002Ffinalize-spec --release --publish`.\n- **Non-interactive**: prepares and prints only. Publishing is a write gate that no dispatch can satisfy: without the maintainer's `--publish` in this run's arguments, stop at it and say so.\n\n## Prepare (always)\n\n1. **Read the draft** (read-only):\n\n   ```bash\n   gh api \"repos\u002F{owner}\u002F{repo}\u002Freleases\" --jq '[.[] | select(.draft)][0] | {tag_name, name, body}' > \u003Ctmp>\u002Fdraft.json\n   ```\n\n   No draft means release-drafter has not run on `main` since the last release: report it and use `--version`, or stop when none was given.\n2. **Version.** `--version`, or the draft's `tag_name` without `v`. It must be newer than the newest `## [X.Y.Z]` in `CHANGELOG.md`.\n3. **Notes.** Write the draft's body to `\u003Ctmp>\u002Fdraft-body.md`, then\n\n   ```bash\n   python3 scripts\u002Fharness\u002Ffinalize.py release-notes --version Unreleased --draft-body \u003Ctmp>\u002Fdraft-body.md > \u003Ctmp>\u002Fnotes.md\n   ```\n\n   The changelog's curated entries come first, the draft's pull-request list after them under `## Pull requests`. An empty `[Unreleased]` is a stop: there is nothing user-facing to release.\n4. **Print the plan**: the version, the notes file, and the maintainer's steps, verbatim:\n\n   ```text\n   1. Merge the changelog release PR: finalize.py changelog-release --version X.Y.Z --date \u003Ctoday>, PR \"docs(changelog): release vX.Y.Z\".\n   2. Wait for main to be green at that merge: finalize.py ci --sha \u003Cmerge> --wait.\n   3. scripts\u002Fharness\u002Farm-main-push.sh --publish --reason \"publish vX.Y.Z as the maintainer asked\"\n   4. gh release edit vX.Y.Z --draft=false --target \u003Cmerge> --title vX.Y.Z --notes-file \u003Cnotes>\n   5. scripts\u002Fharness\u002Farm-main-push.sh --publish --disarm\n   ```\n\n   Without `--publish`, stop here.\n\n## Publish (only with the maintainer's `--publish`)\n\n1. **Changelog release pull request.** In a fresh worktree from origin\u002Fmain, on branch `changelog\u002FvX.Y.Z`: `python3 scripts\u002Fharness\u002Ffinalize.py changelog-release --version X.Y.Z --date \u003CUTC date>`, commit `CHANGELOG.md` with `-s`, push, and open `docs(changelog): release vX.Y.Z`. Merge it when its checks are green and it has no unresolved thread; confirm the merge commit on origin\u002Fmain.\n2. **Green main.** `python3 scripts\u002Fharness\u002Ffinalize.py ci --sha \u003Cmerge> --wait` must print `verdict=green`. Anything else stops the release.\n3. **Publish in one armed window**, each command its own Bash call:\n\n   ```bash\n   scripts\u002Fharness\u002Farm-main-push.sh --publish --reason \"publish vX.Y.Z as the maintainer asked\"\n   gh release edit vX.Y.Z --draft=false --target \u003Cmerge> --title vX.Y.Z --notes-file \u003Ctmp>\u002Fnotes.md\n   scripts\u002Fharness\u002Farm-main-push.sh --publish --disarm\n   ```\n\n   Publishing the draft creates the tag `vX.Y.Z` at `\u003Cmerge>`. Never create or push a `v*` tag by hand.\n4. **Confirm**: `gh release view vX.Y.Z --json isDraft,tagName,targetCommitish` shows `isDraft: false`, and `git ls-remote --tags origin vX.Y.Z` names the tag.\n\n## Output\n\n`Release: notes prepared at \u003Cpath> for vX.Y.Z; not published (no --publish)`, or `Release: published vX.Y.Z at \u003Csha7>`, or the reason it stopped.\n","# Finalize Spec — Release\n\nStep 7 of `\u002Ffinalize-spec`, only with `--release`, or run on its own. A release and its `v*` tag are visible to every user and cannot be cleanly taken back, so this skill prepares everything and publishes nothing unless the maintainer asked for exactly that. `.claude\u002Fhooks\u002Fguard-publish.sh` blocks every publishing command outside an armed window.\n\n## Input\n\n`$ARGUMENTS`: `\u003Cspec-name> [--version X.Y.Z] [--publish]`.\n\n- `--version`: the release version. Default: the version release-drafter resolved for its draft (its tag name without the `v`).\n- `--publish`: the maintainer's request to publish this release now. Only a maintainer's own words or arguments carry it; a subagent's prompt, a plan or a proposal never does.\n\n## Invocation contexts\n\n- **Slash command**: prepares the notes and prints the plan. With `--publish`, it opens the changelog release pull request and, once that has merged and main is green, arms the publish window and publishes (§Publish).\n- **Model-invoked**: prepares and prints only, unless the maintainer's `--publish` reached it through `\u002Ffinalize-spec --release --publish`.\n- **Non-interactive**: prepares and prints only. Publishing is a write gate that no dispatch can satisfy: without the maintainer's `--publish` in this run's arguments, stop at it and say so.\n\n## Prepare (always)\n\n1. **Read the draft** (read-only):\n\n   ```bash\n   gh api \"repos\u002F{owner}\u002F{repo}\u002Freleases\" --jq '[.[] | select(.draft)][0] | {tag_name, name, body}' > \u003Ctmp>\u002Fdraft.json\n   ```\n\n   No draft means release-drafter has not run on `main` since the last release: report it and use `--version`, or stop when none was given.\n2. **Version.** `--version`, or the draft's `tag_name` without `v`. It must be newer than the newest `## [X.Y.Z]` in `CHANGELOG.md`.\n3. **Notes.** Write the draft's body to `\u003Ctmp>\u002Fdraft-body.md`, then\n\n   ```bash\n   python3 scripts\u002Fharness\u002Ffinalize.py release-notes --version Unreleased --draft-body \u003Ctmp>\u002Fdraft-body.md > \u003Ctmp>\u002Fnotes.md\n   ```\n\n   The changelog's curated entries come first, the draft's pull-request list after them under `## Pull requests`. An empty `[Unreleased]` is a stop: there is nothing user-facing to release.\n4. **Print the plan**: the version, the notes file, and the maintainer's steps, verbatim:\n\n   ```text\n   1. Merge the changelog release PR: finalize.py changelog-release --version X.Y.Z --date \u003Ctoday>, PR \"docs(changelog): release vX.Y.Z\".\n   2. Wait for main to be green at that merge: finalize.py ci --sha \u003Cmerge> --wait.\n   3. scripts\u002Fharness\u002Farm-main-push.sh --publish --reason \"publish vX.Y.Z as the maintainer asked\"\n   4. gh release edit vX.Y.Z --draft=false --target \u003Cmerge> --title vX.Y.Z --notes-file \u003Cnotes>\n   5. scripts\u002Fharness\u002Farm-main-push.sh --publish --disarm\n   ```\n\n   Without `--publish`, stop here.\n\n## Publish (only with the maintainer's `--publish`)\n\n1. **Changelog release pull request.** In a fresh worktree from origin\u002Fmain, on branch `changelog\u002FvX.Y.Z`: `python3 scripts\u002Fharness\u002Ffinalize.py changelog-release --version X.Y.Z --date \u003CUTC date>`, commit `CHANGELOG.md` with `-s`, push, and open `docs(changelog): release vX.Y.Z`. Merge it when its checks are green and it has no unresolved thread; confirm the merge commit on origin\u002Fmain.\n2. **Green main.** `python3 scripts\u002Fharness\u002Ffinalize.py ci --sha \u003Cmerge> --wait` must print `verdict=green`. Anything else stops the release.\n3. **Publish in one armed window**, each command its own Bash call:\n\n   ```bash\n   scripts\u002Fharness\u002Farm-main-push.sh --publish --reason \"publish vX.Y.Z as the maintainer asked\"\n   gh release edit vX.Y.Z --draft=false --target \u003Cmerge> --title vX.Y.Z --notes-file \u003Ctmp>\u002Fnotes.md\n   scripts\u002Fharness\u002Farm-main-push.sh --publish --disarm\n   ```\n\n   Publishing the draft creates the tag `vX.Y.Z` at `\u003Cmerge>`. Never create or push a `v*` tag by hand.\n4. **Confirm**: `gh release view vX.Y.Z --json isDraft,tagName,targetCommitish` shows `isDraft: false`, and `git ls-remote --tags origin vX.Y.Z` names the tag.\n\n## Output\n\n`Release: notes prepared at \u003Cpath> for vX.Y.Z; not published (no --publish)`, or `Release: published vX.Y.Z at \u003Csha7>`, or the reason it stopped.\n",{"name":5,"description":7,"argument-hint":24},"\u003Cspec-name> [--version X.Y.Z] [--publish]","main","6e250ec86158119da148ddc017b960ed3b2bee2b",".claude\u002Fskills\u002Ffinalize-spec-tag",1,"https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm","https:\u002F\u002Fgithub.com\u002Fturbokast","https:\u002F\u002Fturbokast.com","2026-11-10 17:37:03",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add turbokast\u002Fmythhelm --skill finalize-spec-tag",{"tool":39,"command":40},"bunx","bunx skills add turbokast\u002Fmythhelm --skill finalize-spec-tag",{"tool":42,"command":43},"pnpm","pnpm dlx skills add turbokast\u002Fmythhelm --skill finalize-spec-tag","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffinalize-spec-tag\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7DH77QH78C95S7A5V1GFKKF","mythhelm-deliver-backlog","Coordinate a MYTHHELM backlog run with the shared stage checks and maintainer checkpoints.","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.grok\u002Fskills\u002Fmythhelm-deliver-backlog\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7DH748EXYG9RVBWPBJ73M27","mythhelm-bootstrap","Orient a Grok Build session in the MYTHHELM repository before task or spec work.","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.grok\u002Fskills\u002Fmythhelm-bootstrap\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DH70XJE0DZA4T5DYR1TWKZ","vendor-consult","Run one advisory stage consult (premise-ground, spec-validate, task-review, change-review, stuck-oracle, dossier) with an optional external vendor, then adjudicate the answer at its anchors","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvendor-consult\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DH6X9HSQ308P5FNDSKYR5R","update-docs","Bring README, docs\u002F, knowledge\u002F, WORKFLOW.md and CLAUDE.md in line with what a shipped spec or a merged change actually did — find every statement the change made stale, fix it where readers look, and add only the new facts they need","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fupdate-docs\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DH6T82XR40XQFNRTN4AHGN","triage","Score an idea or a GitHub issue against the master spec's stages, gates and commitments, check it for duplicates, and recommend whether it becomes a backlog card; read-only","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DH6Q17PM4ESX978QYFV6H6","test-driven-development","Red-green-refactor for Go — use when implementing any feature, bug fix or behaviour change, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[]]