[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M753WD31MWBAXDND6CPPQKCB":3,"skill-same:01M753WD31MWBAXDND6CPPQKCB":56},{"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":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M753WD31MWBAXDND6CPPQKCB","release",null,"Use when cutting a release — tagging a version, pushing tags, publishing a GitHub release, or shipping this toolkit's plugins. Detects the repo's release machinery (AGENTS.md release section, changesets, claude plugin tag, plain git tag + gh release), always shows a dry-run plan first, and executes only on one confirm. Triggers include \"cut a release\", \"release v1.2.3\", \"tag and publish\", \"ship a new version\", \"whats in the next release\".","jabworks\u002Fagentic-toolkit","jabworks","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F159094119?v=4","01M753P4JBZBTT7WN1PJBPZJZP","JAB Works","01M753P4K5KDGEWGXWT811BZET",2,"MIT","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Frelease\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: release\ndescription: Use when cutting a release — tagging a version, pushing tags, publishing a GitHub release, or shipping this toolkit's plugins. Detects the repo's release machinery (AGENTS.md release section, changesets, claude plugin tag, plain git tag + gh release), always shows a dry-run plan first, and executes only on one confirm. Triggers include \"cut a release\", \"release v1.2.3\", \"tag and publish\", \"ship a new version\", \"whats in the next release\".\nwhen_to_use: Cutting the release itself. Not for deciding a plugin or skill's semver bump beforehand — that's toolkit-change-control; in jabworks\u002Fagentic-toolkit, run that gate first and release the version it picks. Not for everyday undo\u002Frecovery git work — that's git-operations.\n---\n\n# \u002Frelease\n\nOne dry-run, one confirm, one release. Never a force-push, never a guess.\n\n## Usage\n\n```\n\u002Frelease                 # detect machinery, propose the next version\n\u002Frelease v1.4.0          # explicit version\n\u002Frelease minor           # bump hint\n```\n\n## When NOT to use\n\n- Committing the work → `git-commit` (it stops before push; this skill starts\n  after the commits exist).\n- Undo \u002F discard \u002F stash \u002F recovery → `git-operations`.\n- \"Is this toolkit change *ready* to publish?\" → `toolkit-change-control` gates;\n  this skill executes.\n- Deploying to servers or infrastructure — out of scope.\n\n## Guards — all must pass before anything else\n\nEach failure names its fix and ends the attempt. **`--force` is banned. History\nrewrites are banned.**\n\n```\n□ Working tree clean              → commit (git-commit) or park it (git-operations)\n□ HEAD is an ancestor of main    → git merge-base --is-ancestor HEAD origin\u002Fmain\n                                    (merge first — tags on dead branches haunt forever)\n□ Test gate green                 → AGENTS.md test\u002Ffinalize command; node --test here\n□ Version consistent              → tag must equal the manifest\u002Fpackage version\n                                    (claude plugin tag validates this natively)\n□ Tag doesn't already exist       → git tag -l \u003Ctag>; git ls-remote --tags origin\n□ gh authenticated                → gh auth status\n```\n\n## The Router — first match wins\n\n1. **AGENTS.md `release:` \u002F `## Release` section** → follow the project's own\n   process verbatim. The project override always wins.\n2. **Changesets** (`.changeset\u002F` exists) → changesets owns versioning and the\n   CHANGELOG — never hand-tag on top of it:\n   - `npx changeset status` to see what's pending.\n   - If a changesets GitHub Action manages \"Version Packages\" PRs, the release\n     **is** merging that PR — guide the user there and stop.\n   - Otherwise: `npx changeset version` → show the diff → confirm →\n     `npx changeset publish` → `git push --follow-tags`.\n3. **This toolkit** (`.claude-plugin\u002Fmarketplace.json` exists) — **plugin\n   releases are automated; do not hand-tag**:\n   - Merging to `main` runs `.github\u002Fworkflows\u002Fplugin-release.yml`, which calls\n     `scripts\u002Frelease-plugins.mjs --since \u003Cpush-base> --execute`: every plugin\n     version *introduced by that push* gets its `\u003Cname>--v\u003Cversion>` tag and a\n     GitHub release, with notes from the commits that touched its dist tree.\n     CI never backfills — a gap stays a gap until someone runs `--initial`.\n   - The release *is* merging the PR. Confirm the version bump landed and stop.\n   - Before committing a bump: `node scripts\u002Frelease-plugins.mjs` to see the\n     plan, and `--write-changelog` to regenerate `CHANGELOG.md` — a test fails\n     when a shipped version has no entry.\n   - Versions on an unmerged branch are held back by design; the script refuses\n     to release a commit that is not on the default branch.\n   - If a tag lands but its release does not (they are two calls, and the\n     second can fail alone), `--repair` creates the missing releases. A tag\n     with no release is otherwise stranded forever.\n   - Hand-tagging remains the fallback if the workflow is broken:\n     `claude plugin tag dist\u002Fplugins\u002F\u003Cname>` validates plugin.json against the\n     marketplace entry, then `git push origin \u003Ctag>` and\n     `gh release create \u003Ctag> --generate-notes --title \"\u003Cname> v\u003Cversion>\"`.\n   - Remind: installed copies refresh only on a version change — users must\n     update the plugin.\n4. **Generic GitHub project**:\n   - Propose the version from conventional commits since\n     `git describe --tags --abbrev=0` (feat → minor, fix → patch,\n     BREAKING CHANGE → major).\n   - Annotated tag `vX.Y.Z` → `git push origin vX.Y.Z` →\n     `gh release create vX.Y.Z --generate-notes`.\n   - **npm publish never happens on this branch** — only via branch 1 or 2.\n\nGitLab\u002FBitbucket: no route yet — say so and stop rather than improvise.\n\n## Dry-Run Plan — always, before touching anything\n\n```\n## Release plan: \u003Crepo> — \u003CvX.Y.Z | \"merge Version Packages PR\">\nMachinery   AGENTS.md | changesets | toolkit | generic-github\nVersion     \u003Ccurrent> → \u003Cproposed>   (N feats, M fixes since \u003Clast tag>)\nCommits     \u003Cgit log --oneline \u003Clast-tag>..HEAD>\nNotes       \u003Cgh api repos\u002F{owner}\u002F{repo}\u002Freleases\u002Fgenerate-notes -f tag_name=\u003Ctag>>\nWill run    1. \u003Cexact command>  2. …  3. …\nRollback    per step — references\u002Frollback.md\n```\n\nThen ask once: **\"Execute this release? [y\u002Fn]\"** One yes runs the whole\nsequence. Any step failure → stop, report what completed and what's reversible,\nwith the rollback command for the completed steps. Never retry-loop.\n\n## Evidence\n\nEvery step prints its verification (tag exists locally and on the remote,\nrelease URL, publish output). Final line: the release URL plus the rollback\none-liner.\n\n## Common traps\n\n| Trap | Reality |\n|---|---|\n| \"Just force-push the fixed tag\" | Never. Delete + re-tag via the rollback path, or fix forward with the next patch version. |\n| Hand-tagging in a changesets repo | Changesets owns versions — you'll fork the changelog. Use the changesets route. |\n| Releasing from a feature branch | The ancestor-of-main guard exists because published tags on unmerged branches haunt forever. |\n| Skipping the dry-run \"because it's just a patch\" | The dry-run IS the safety, and it costs one screen. |\n| Toolkit release without a version bump | Installed caches keep serving the old copy. |\n\n## Related skills\n\n`git-commit` (gets the work committed — stops before push by design, hands off\nhere), `git-operations` (undo\u002Frecovery, including tag-deletion mechanics),\n`toolkit-change-control` (publish-readiness gate for this repo — it gates, this\nexecutes), condux `workflow` CP-3 (routes here after everything is green).\n\n## Provenance and maintenance\n\nRe-verify volatile claims with:\n- `claude plugin tag --help` — the toolkit tag+validate primitive\n- `gh api repos\u002F{owner}\u002F{repo}\u002Freleases\u002Fgenerate-notes -f tag_name=\u003Ctag>` — notes preview\n- `npx changeset status` — changesets detection behavior\n\nLast generated: 2026-07-08\nKnown uncertainty:\n- The guard set is adopted from claude-sdlc-wizard's release post-mortems\n  (ancestry + version-match); not yet exercised by a real failure here.\n- GitHub-only: `gh` paths assume github.com remotes; GitLab\u002FBitbucket routes\n  are reserved, unbuilt.\n","# \u002Frelease\n\nOne dry-run, one confirm, one release. Never a force-push, never a guess.\n\n## Usage\n\n```\n\u002Frelease                 # detect machinery, propose the next version\n\u002Frelease v1.4.0          # explicit version\n\u002Frelease minor           # bump hint\n```\n\n## When NOT to use\n\n- Committing the work → `git-commit` (it stops before push; this skill starts\n  after the commits exist).\n- Undo \u002F discard \u002F stash \u002F recovery → `git-operations`.\n- \"Is this toolkit change *ready* to publish?\" → `toolkit-change-control` gates;\n  this skill executes.\n- Deploying to servers or infrastructure — out of scope.\n\n## Guards — all must pass before anything else\n\nEach failure names its fix and ends the attempt. **`--force` is banned. History\nrewrites are banned.**\n\n```\n□ Working tree clean              → commit (git-commit) or park it (git-operations)\n□ HEAD is an ancestor of main    → git merge-base --is-ancestor HEAD origin\u002Fmain\n                                    (merge first — tags on dead branches haunt forever)\n□ Test gate green                 → AGENTS.md test\u002Ffinalize command; node --test here\n□ Version consistent              → tag must equal the manifest\u002Fpackage version\n                                    (claude plugin tag validates this natively)\n□ Tag doesn't already exist       → git tag -l \u003Ctag>; git ls-remote --tags origin\n□ gh authenticated                → gh auth status\n```\n\n## The Router — first match wins\n\n1. **AGENTS.md `release:` \u002F `## Release` section** → follow the project's own\n   process verbatim. The project override always wins.\n2. **Changesets** (`.changeset\u002F` exists) → changesets owns versioning and the\n   CHANGELOG — never hand-tag on top of it:\n   - `npx changeset status` to see what's pending.\n   - If a changesets GitHub Action manages \"Version Packages\" PRs, the release\n     **is** merging that PR — guide the user there and stop.\n   - Otherwise: `npx changeset version` → show the diff → confirm →\n     `npx changeset publish` → `git push --follow-tags`.\n3. **This toolkit** (`.claude-plugin\u002Fmarketplace.json` exists) — **plugin\n   releases are automated; do not hand-tag**:\n   - Merging to `main` runs `.github\u002Fworkflows\u002Fplugin-release.yml`, which calls\n     `scripts\u002Frelease-plugins.mjs --since \u003Cpush-base> --execute`: every plugin\n     version *introduced by that push* gets its `\u003Cname>--v\u003Cversion>` tag and a\n     GitHub release, with notes from the commits that touched its dist tree.\n     CI never backfills — a gap stays a gap until someone runs `--initial`.\n   - The release *is* merging the PR. Confirm the version bump landed and stop.\n   - Before committing a bump: `node scripts\u002Frelease-plugins.mjs` to see the\n     plan, and `--write-changelog` to regenerate `CHANGELOG.md` — a test fails\n     when a shipped version has no entry.\n   - Versions on an unmerged branch are held back by design; the script refuses\n     to release a commit that is not on the default branch.\n   - If a tag lands but its release does not (they are two calls, and the\n     second can fail alone), `--repair` creates the missing releases. A tag\n     with no release is otherwise stranded forever.\n   - Hand-tagging remains the fallback if the workflow is broken:\n     `claude plugin tag dist\u002Fplugins\u002F\u003Cname>` validates plugin.json against the\n     marketplace entry, then `git push origin \u003Ctag>` and\n     `gh release create \u003Ctag> --generate-notes --title \"\u003Cname> v\u003Cversion>\"`.\n   - Remind: installed copies refresh only on a version change — users must\n     update the plugin.\n4. **Generic GitHub project**:\n   - Propose the version from conventional commits since\n     `git describe --tags --abbrev=0` (feat → minor, fix → patch,\n     BREAKING CHANGE → major).\n   - Annotated tag `vX.Y.Z` → `git push origin vX.Y.Z` →\n     `gh release create vX.Y.Z --generate-notes`.\n   - **npm publish never happens on this branch** — only via branch 1 or 2.\n\nGitLab\u002FBitbucket: no route yet — say so and stop rather than improvise.\n\n## Dry-Run Plan — always, before touching anything\n\n```\n## Release plan: \u003Crepo> — \u003CvX.Y.Z | \"merge Version Packages PR\">\nMachinery   AGENTS.md | changesets | toolkit | generic-github\nVersion     \u003Ccurrent> → \u003Cproposed>   (N feats, M fixes since \u003Clast tag>)\nCommits     \u003Cgit log --oneline \u003Clast-tag>..HEAD>\nNotes       \u003Cgh api repos\u002F{owner}\u002F{repo}\u002Freleases\u002Fgenerate-notes -f tag_name=\u003Ctag>>\nWill run    1. \u003Cexact command>  2. …  3. …\nRollback    per step — references\u002Frollback.md\n```\n\nThen ask once: **\"Execute this release? [y\u002Fn]\"** One yes runs the whole\nsequence. Any step failure → stop, report what completed and what's reversible,\nwith the rollback command for the completed steps. Never retry-loop.\n\n## Evidence\n\nEvery step prints its verification (tag exists locally and on the remote,\nrelease URL, publish output). Final line: the release URL plus the rollback\none-liner.\n\n## Common traps\n\n| Trap | Reality |\n|---|---|\n| \"Just force-push the fixed tag\" | Never. Delete + re-tag via the rollback path, or fix forward with the next patch version. |\n| Hand-tagging in a changesets repo | Changesets owns versions — you'll fork the changelog. Use the changesets route. |\n| Releasing from a feature branch | The ancestor-of-main guard exists because published tags on unmerged branches haunt forever. |\n| Skipping the dry-run \"because it's just a patch\" | The dry-run IS the safety, and it costs one screen. |\n| Toolkit release without a version bump | Installed caches keep serving the old copy. |\n\n## Related skills\n\n`git-commit` (gets the work committed — stops before push by design, hands off\nhere), `git-operations` (undo\u002Frecovery, including tag-deletion mechanics),\n`toolkit-change-control` (publish-readiness gate for this repo — it gates, this\nexecutes), condux `workflow` CP-3 (routes here after everything is green).\n\n## Provenance and maintenance\n\nRe-verify volatile claims with:\n- `claude plugin tag --help` — the toolkit tag+validate primitive\n- `gh api repos\u002F{owner}\u002F{repo}\u002Freleases\u002Fgenerate-notes -f tag_name=\u003Ctag>` — notes preview\n- `npx changeset status` — changesets detection behavior\n\nLast generated: 2026-07-08\nKnown uncertainty:\n- The guard set is adopted from claude-sdlc-wizard's release post-mortems\n  (ancestry + version-match); not yet exercised by a real failure here.\n- GitHub-only: `gh` paths assume github.com remotes; GitLab\u002FBitbucket routes\n  are reserved, unbuilt.\n",{"name":5,"description":7,"when_to_use":24},"Cutting the release itself. Not for deciding a plugin or skill's semver bump beforehand — that's toolkit-change-control; in jabworks\u002Fagentic-toolkit, run that gate first and release the version it picks. Not for everyday undo\u002Frecovery git work — that's git-operations.","main","5277649b071c1c0cdf4f15eee861b1608fc1bbcb","skills\u002Frelease",0,"https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit","https:\u002F\u002Fgithub.com\u002Fjabworks","2026-11-03 15:03:51",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add jabworks\u002Fagentic-toolkit --skill release",{"tool":38,"command":39},"bunx","bunx skills add jabworks\u002Fagentic-toolkit --skill release",{"tool":41,"command":42},"pnpm","pnpm dlx skills add jabworks\u002Fagentic-toolkit --skill release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Frelease\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"evals\u002Ftrigger_eval.json","REFERENCE","参考文档",2676,"https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Frelease\u002Fevals\u002Ftrigger_eval.json",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Frollback.md",1824,"https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Frelease\u002Freferences\u002Frollback.md",[57,63,69,76,83,90],{"skillNo":58,"name":59,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7540BPNTFZH7V41P5E2S692","orphan","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcomposition\u002Fbad\u002Fskills\u002Forphan\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":6,"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},"01M7540AG2KFTQ8DJMNV6806MV","no-blurb","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcomposition\u002Fbad\u002Fskills\u002Fno-blurb\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},"01M75404N306PY1JFPQ0GGNTYB","workflow","Routes any dev task into the right execution tier (Small\u002FMedium\u002FLarge) and carries condux's operating rules — proportional effort, lazy skill loading, soft gates, implement-yourself-by-default.","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\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},"01M753ZZ6TTA06GRJAG679BQ2H","usage-trace","Checks and manages durable, local usage capture — ingest, health status, and the opt-in limit snapshot — for Claude Code and Codex. Capture itself runs automatically at session start.","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fusage-trace\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},"01M753ZSKJSF8WFS7AXR2N65SE","toolkit-skill-standards","Use when writing or reviewing a SKILL.md for jabworks\u002Fagentic-toolkit — frontmatter budgets, the trigger contract (\"Use when…\" description or when_to_use field), progressive disclosure into references\u002F, and keeping a new description out of existing skills' trigger space. Triggers include \"review this skill description\", \"write the frontmatter\", \"does this collide with an existing skill\", \"where should this content live\". Not for scaffold\u002Fsync mechanics; use toolkit-foundry.","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Ftoolkit-skill-standards\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M753ZKX3KTVYWX15A9A0WZN0","toolkit-research-frontier","Use when planning improvement work on jabworks\u002Fagentic-toolkit itself — open problems (trigger-collision automation, YAML-strict frontmatter checks, docs-catalog enforcement), existing assets, the next three concrete steps, and the four-front library-health campaign with commands and success criteria. Triggers include \"let's improve our toolkit\", \"let's improve this repo\", \"what should we improve next\", \"toolkit roadmap\", \"open problems\", \"run the health campaign\".","https:\u002F\u002Fgithub.com\u002Fjabworks\u002Fagentic-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Ftoolkit-research-frontier\u002FSKILL.md",[],[]]