[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B3P7D39QHT9XTCK42F79P9":3,"skill-same:01M7B3P7D39QHT9XTCK42F79P9":84},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7B3P7D39QHT9XTCK42F79P9","ship",null,"Ship the current branch — evaluate its SemVer release impact, refresh the docs, write the changelog entry for the version this merge will mint, file its human follow-ups, run the fast checks, push, and open or update the PR. Use when a feature branch is ready for review, or when the user says \"ship it\", \"open a PR\", or \"push this\".","jwh3times\u002Fcauset","jwh3times","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1965019?v=4","01M720KXPKWJRK0WCC0ZD480M7","Jerry Holland","01M7B3ME1K8ZQAEB7NRCEQ8SXV",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ship\ndescription: Ship the current branch — evaluate its SemVer release impact, refresh the docs, write the changelog entry for the version this merge will mint, file its human follow-ups, run the fast checks, push, and open or update the PR. Use when a feature branch is ready for review, or when the user says \"ship it\", \"open a PR\", or \"push this\".\nmetadata:\n  settings: workspace issue-tracker human-follow-up releases ship dev-flow triage-labels agents-md\n---\n\n# Ship\n\nTake the current branch from \"code is done\" to \"PR is open and green-able\", with a changelog that\nnames the version this merge will actually create.\n\n**Announce at start:** \"I'm using the ship skill to open a PR for this branch.\"\n\nRun shell snippets in bash (Git Bash on Windows). Where `gh` is unavailable, use the equivalent\nGitHub MCP operation: a missing CLI changes the interface, not the step or its completion\ncriterion.\n\n`ship` stops at \"PR open\". It never merges, never pushes to `main`, never force-pushes, and never\nruns the full test suites: CI owns them, and running them here makes the skill slow.\n\n## 0. Settings\n\nThis skill reads `docs\u002Fagents\u002Fworkspace.md`, `docs\u002Fagents\u002Fissue-tracker.md`,\n`docs\u002Fagents\u002Fhuman-follow-up.md`, `docs\u002Fagents\u002Freleases.md`, `docs\u002Fagents\u002Fship.md` and\n`docs\u002Fagents\u002Fdev-flow.md`. Follow\n`.agents\u002Fskills\u002Fship\u002Fsettings\u002FREADME.md` to read them and complete any that are missing; the\ndefinitions sit beside it. Resolve each `discover:` value once, here, and\nreuse it below.\n\nWith `Scheme: none`, skip every step marked **(release)**.\n\n## 1. Preconditions — stop if any fail\n\n- **Not on `main`.** Work happens on a branch. On `main`, stop and offer to create one named by the\n  `Issue link` branch pattern (`\u003Ctype>\u002F\u003Cslug>` when it is `none`).\n- **Clean tree.** `git status --porcelain` prints nothing but the settings files step 0 just wrote,\n  which go into this run's commit. Otherwise stop and ask whether to commit what is there; never\n  commit it silently. Once answered, restart from this step. Every change staged later was then\n  made by this run.\n- **GitHub reachable.** `gh auth status` succeeds, or GitHub MCP can reach this repository.\n- **Companion in step.** When the `Private companion` is set and its checkout exists, run the\n  `Workspace status command`: the companion must be clean and neither ahead of nor behind its\n  upstream. An absent checkout is a valid state; report it.\n- **Up to date with `main`.**\n\n  ```bash\n  git fetch -q --tags origin\n  git merge-base --is-ancestor origin\u002Fmain HEAD && echo current || echo behind\n  ```\n\n  When behind, offer to `git merge origin\u002Fmain` now, and resolve conflicts with the user. Never\n  rebase a pushed branch.\n\nUse `origin\u002Fmain` throughout, never local `main`: a stale local `main` silently widens the diff to\nwork already merged, and a clone that fetched only this branch has none.\n\n## 2. Evaluate the release impact (release)\n\nRead the whole branch, not its latest commit:\n\n```bash\nbase=\"$(git merge-base origin\u002Fmain HEAD)\"\ngit diff --stat \"$base\"..HEAD\ngit log --format='%s%n%b' \"$base\"..HEAD\ngit diff \"$base\"..HEAD\n```\n\nThe stat and the log are an index. Read the diff, and the tests and docs it touches, before\ndeciding. Classify the impact to **this project**, highest level present:\n\n- **Major** — an existing public behavior, API, URL, persisted-data shape, configuration,\n  deployment contract or established user workflow becomes incompatible, and its users must\n  migrate. On a `0.y` line, an incompatible change is minor unless the branch deliberately cuts\n  `1.0.0`.\n- **Minor** — a backwards-compatible capability or a material expansion of behavior, or a\n  deliberate platform or toolchain generation change that raises the supported baseline.\n- **Build** — fixes (security fixes included), dependency maintenance, refactors, tests, docs,\n  tooling: nothing that adds capability or raises a baseline.\n\nJudge this project's contracts, not a dependency's version number. Release metadata and generated\nmirrors are not evidence. With `Scheme: per-merge`, the cumulative content of `Unreleased` counts\ntoo. A level the user asked for is still evaluated; when the evaluation differs, show both and ask.\n\nRecord `Release level: \u003Cmajor|minor|build> — \u003Cone-sentence rationale>`. Steps 9 and 10 use that\nexact line.\n\n**Apply it.** The baseline is the higher of the newest three-part `v*` tag (ignoring the\n`Skipped tags` **Ignore** patterns) and the `Version file` on `origin\u002Fmain` (`git show \"origin\u002Fmain:\u003Cfile>\"`).\n\n- **Build** — the `Version file` stays at its `origin\u002Fmain` value. Restore it if the branch moved it\n  without release intent.\n- **Minor** — the target line is `\u003Cmajor>.\u003Cminor + 1>.0` of the baseline.\n- **Major** — the target line is `\u003Cmajor + 1>.0.0`.\n\nFor major or minor, follow `Ask before bumping` first, then run `Bump command` with the exact\ntarget, so a re-run lands on the same value instead of advancing twice. Check that the version file\nand any lockfile beside it agree. A branch that already carries the target keeps it; a branch that\ncarries a different line was bumped on purpose: ask before replacing it.\n\n## 3. Compute the target version (release)\n\n- **`per-merge`** — first confirm the newest merge on `origin\u002Fmain` is tagged:\n\n  ```bash\n  git tag --points-at origin\u002Fmain -l 'v*'\n  ```\n\n  Empty output means the tag workflow has not finished for a merge that just landed, and the next\n  version would repeat a taken number. Wait for the workflow, fetch tags again, and re-check; if it\n  stays untagged after the workflow finished, ask the user. Then run `Next-version command`. It\n  prints a bare SemVer and is the single source of truth: never compute the build number yourself.\n\n  Check whether another open PR already claims that version. `gh pr diff` takes no path, so cut\n  the `CHANGELOG.md` part out of each diff:\n\n  ```bash\n  branch=\"$(git branch --show-current)\"\n  gh pr list --state open --json number,headRefName --jq '.[] | \"\\(.number) \\(.headRefName)\"' |\n    while read -r number head; do\n      [ \"$head\" = \"$branch\" ] && continue\n      gh pr diff \"$number\" | sed -n '\u002F^diff --git a\\\u002FCHANGELOG.md \u002F,\u002F^diff --git\u002Fp' |\n        grep '^+## \\[' | sed \"s\u002F^\u002F#$number \u002F\"\n    done\n  ```\n\n  If one does, name it in the report: whichever merges second renumbers on its next `ship`.\n- **`cut-on-line`** — a build has no exact target: the next tag assigns it, whether a workflow tags\n  each merge or a maintainer tags a release, and another merge can land first. A confirmed major or\n  minor's target is the new line from step 2.\n\n## 4. Skipped tags (release)\n\nOnly with `Scheme: per-merge` and `Skipped tags` `backfill` or `roll up`. A skipped tag is a merge\nthat wrote no section — a dependency bot's PR, or one opened in the web UI. List them; run the\ncommands exactly, since tags print as `v1.1.5` and sections as `1.1.5`, and comparing raw lists by\neye reports every tag as missing.\n\n- **`backfill`** — every released version with no section:\n\n  ```bash\n  comm -23 \\\n    \u003C(git tag -l 'v*' | sed -nE 's\u002F^v([0-9]+\\.[0-9]+\\.[0-9]+)$\u002F\\1\u002Fp' | sort) \\\n    \u003C(sed -nE 's\u002F^## \\[([0-9]+\\.[0-9]+\\.[0-9]+)\\].*\u002F\\1\u002Fp' CHANGELOG.md | sort)\n  ```\n\n- **`roll up`** — only the versions released after the newest section on `origin\u002Fmain`; older\n  ones were rolled into an earlier section:\n\n  ```bash\n  newest=\"$(git show origin\u002Fmain:CHANGELOG.md |\n    sed -nE 's\u002F^## \\[([0-9]+\\.[0-9]+\\.[0-9]+)\\].*\u002F\\1\u002Fp' | sort -V | tail -1)\"\n  git tag -l 'v*' | sed -nE 's\u002F^v([0-9]+\\.[0-9]+\\.[0-9]+)$\u002F\\1\u002Fp' | sort -V |\n    sed -n \"\u002F^${newest}\\$\u002F,\\$p\" | tail -n +2\n  ```\n\nDrop versions matching the **Ignore** patterns. With `version` set to each one left, read the tag;\nit is the merge commit, so the merged branch is its second parent:\n\n```bash\ngit log -1 --format='%cs' \"v$version\"                  # the section's date\ngit log --format='%s%n%b' \"v$version^1..v$version^2\"   # what landed\ngit diff \"v$version^1\" \"v$version\" --stat              # manifests and lockfiles it changed\ngit log -1 --format=%an \"v$version^2\"                  # dependabot[bot] for a bot PR\n```\n\nKeep it factual: name the packages and versions, and call a lockfile-only change transitive.\nAttribute to a bot only when the second parent's author is the bot: the merge commit's author is\nwhoever clicked Merge. When `^2` does not exist (a squash or fast-forward), read the tag's own\ncommit.\n\n- **`backfill`** — add a dated section for each version in place, newest first.\n- **`roll up`** — invent no section; step 7 writes their changes into this branch's section.\n\n## 5. Refresh the docs\n\nRun the `docs-updater` skill in `fix` mode, scoped to this branch's diff, not a full audit — in a\nsubagent where the harness has one, told to follow `.agents\u002Fskills\u002Fdocs-updater\u002FSKILL.md`;\notherwise follow it yourself. A subagent cannot ask the user, so complete its settings first, here,\nby following its step 0.\n\n```bash\nrange=\"$(git merge-base origin\u002Fmain HEAD)..HEAD\"\n```\n\nTell it what changed and why, that it was invoked by `ship` on an unmerged branch, and that this\nskill writes the changelog and the `Version file`. It leaves its edits uncommitted and returns the\nhuman actions it found for step 6, and any wiki search it owes after the merge (the\n`Follow-up wiki`, or a `Doc map` item in a wiki).\nCompanion edits are committed there as its own repository, never in this one: run the\n`## Procedure` in `.agents\u002Fskills\u002Fship\u002Fsettings\u002Fworkspace.md`.\n\n## 6. Human follow-ups\n\nRun the `## Procedure` in `.agents\u002Fskills\u002Fship\u002Fsettings\u002Fhuman-follow-up.md` for every required human\naction this branch leaves, before the PR opens, including those `docs-updater` returned. Reconcile\nrather than duplicate; on a re-ship, reuse the records already made. A follow-up never lives only\nin the changelog or the PR body. Its links go in the report and private records, never in the\npublic PR.\n\n## 7. Write the changelog (release)\n\nWrite user-visible behavior and its consequences, derived from the diff — not a commit log. Use the\nheadings the file already uses (Keep a Changelog: `Added`, `Changed`, `Deprecated`, `Removed`,\n`Fixed`, `Security`, plus any the file adds), one of each per section, and match its voice. Dates\nare today's, `YYYY-MM-DD`.\n\n**Idempotent.** List the sections this branch added:\n\n```bash\ngit diff origin\u002Fmain...HEAD -- CHANGELOG.md | grep '^+## \\['\n```\n\nA section listed there is this branch's from an earlier `ship`: rewrite it in place, never stack a\nsecond. Entries this branch added to `Unreleased` are rewritten the same way.\n\n- **`per-merge`** — insert `## [\u003Ctarget>] - \u003Cdate>` directly below `## [Unreleased]`, holding this\n  branch's entries plus anything accumulated in `Unreleased` and, with `roll up`, the changes of\n  the tags step 4 listed; reset `Unreleased` to the\n  `Unreleased placeholder`. When the branch's section names an older version because another PR merged first,\n  **renumber that section** to the target. Then merge `origin\u002Fmain`: their section sits in the same\n  place, so resolve `CHANGELOG.md` keeping both, newest version first, and go back to step 3 — their\n  merge minted a tag, so the target moved again.\n- **`cut-on-line`, build** — add the entries under `Unreleased`, replacing its placeholder. No dated\n  section, no `Version file` edit.\n- **`cut-on-line`, confirmed major or minor** — add the entries under `Unreleased`, move its whole\n  content into `## [\u003Ctarget>] - \u003Cdate>`, and restore the placeholder. When the cut is already there\n  from an earlier `ship`, rewrite this branch's entries inside it; never leave them both above and\n  below the cut.\n\n**Reference links.** When the file ends in a link footer, keep it consistent in the pattern its\nentries follow: `[Unreleased]` compares from the newest version to `HEAD`, and each new or\nrenumbered section — backfilled ones too — gets its own link, newest first.\n\nRun `Changelog check`. A mismatch names the version the merge will really mint: redo this step with\nit.\n\n## 8. Fast checks — refuse to push if any fail\n\nRun every `Fast checks` entry, in order, from its folder; skip a conditional entry only when none of\nits paths changed (`git diff --name-only origin\u002Fmain...HEAD`). They run after the doc and changelog\nedits, because formatters and linters cover those files too.\n\nIf any is red, stop and report; do not push. Offer the entry's fix command. After a fix that writes\nfiles, run the list again from the top: a generated mirror built from unformatted sources is stale\nagain once they are formatted. A check that cannot run here (a missing service, a missing secret) is\nnamed in the report as left to CI.\n\nThen run `Hook: before PR` from `docs\u002Fagents\u002Fship.md`. Its findings go in the report and, where it\nsays, the PR body.\n\n## 9. Commit, push, and open or update the PR\n\nCommit only when `git status --porcelain` shows changes; a re-ship with nothing new makes no empty\ncommit. Staging everything is safe because step 1 proved the tree was clean, and the companion is\nignored, never staged:\n\n```bash\ngit add -A\ngit commit -m \"\u003CRelease commit message, with the real version>\"\ngit push -u origin \"$(git branch --show-current)\"\n```\n\nA rejected push means the remote has commits this checkout lacks: stop and report. Never force-push.\n\n```bash\ngh pr list --head \"$(git branch --show-current)\" --state open --json number,url\n```\n\n- **No PR** → `gh pr create --base main`.\n- **A PR exists** → `gh pr edit \u003Cnumber>` to refresh its body. Never open a second PR.\n\nWrite the body to a temporary file and pass `--body-file`. Fill the repository's PR template\n(`.github\u002Fpull_request_template.md` or `PULL_REQUEST_TEMPLATE.md`) when there is one, from the\nchangelog entries and the diff. Tick a checkbox only on evidence from the diff, the fast checks or\n`Hook: before PR`, and leave the rest unticked; where the template asks how the change was\nverified, name the fast checks actually run and the checks left to CI. Include the\n`Release level:` line from step 2 and, with `per-merge`, the version this merge will mint.\n\n**Issue link**, when the setting is not `none`. The body opens with the link line, in the slot the\ntemplate leaves for it:\n\n- Take `N` from the branch per its **Branch pattern**, and read the issue:\n  `gh issue view \u003CN> --json title,state,labels,body`.\n- The finishing line (`Closes #N`) when this PR finishes the issue; the slice line (`Part of #N`)\n  when it is one slice of a spec that stays open. Each finished issue gets its own keyword:\n  GitHub links only the first issue in `Closes #1 and #2`.\n- A branch with no number: the **Waiver line** when the user waived the flow; no link line for an\n  **Exempt** kind, or for work from a ready issue in the `Private issue repository`.\n- When the branch's number and the issue disagree, or finishing versus slice is unclear, ask before\n  creating the PR. A refreshed body keeps its link line. A number in the title alone links nothing.\n\nWarn, never block, when the PR opens with no link line and neither of those applies, or when the\n`Board` is set and the linked issue is not on it. An issue in the `Private issue repository` is never named in a\npublic PR body, commit message or public issue; it is closed by hand after the merge.\n\nNothing this step writes in public carries a private repository name, link, board number or\ncompanion detail.\n\n## 10. Report\n\n- The PR URL and branch.\n- The `Release level:` line and its evidence; the version this merge will mint (`per-merge`), the\n  new line (a `cut-on-line` cut), or that the next tag assigns the build. Name a competing PR\n  claiming the same version, and say the section is renumbered on a re-ship.\n- What the docs refresh changed, the changelog entries written, and any sections backfilled. When\n  docs-updater owes a wiki search after the merge, say so: the next `end-session` performs it.\n- Human follow-ups: verified issue and wiki links, what is unpublished and why, or that none remain.\n- Fast-check results, checks left to CI, `Hook: before PR` findings, and issue-link warnings.\n- The companion: absent, or clean and in step, and any companion commit made. Never describe the\n  unmerged PR as shipped there.\n- Settings files written in step 0.\n\nSay plainly that the full suites run in CI, not here: the branch is verified only as far as the fast\nchecks go.\n","# Ship\n\nTake the current branch from \"code is done\" to \"PR is open and green-able\", with a changelog that\nnames the version this merge will actually create.\n\n**Announce at start:** \"I'm using the ship skill to open a PR for this branch.\"\n\nRun shell snippets in bash (Git Bash on Windows). Where `gh` is unavailable, use the equivalent\nGitHub MCP operation: a missing CLI changes the interface, not the step or its completion\ncriterion.\n\n`ship` stops at \"PR open\". It never merges, never pushes to `main`, never force-pushes, and never\nruns the full test suites: CI owns them, and running them here makes the skill slow.\n\n## 0. Settings\n\nThis skill reads `docs\u002Fagents\u002Fworkspace.md`, `docs\u002Fagents\u002Fissue-tracker.md`,\n`docs\u002Fagents\u002Fhuman-follow-up.md`, `docs\u002Fagents\u002Freleases.md`, `docs\u002Fagents\u002Fship.md` and\n`docs\u002Fagents\u002Fdev-flow.md`. Follow\n`.agents\u002Fskills\u002Fship\u002Fsettings\u002FREADME.md` to read them and complete any that are missing; the\ndefinitions sit beside it. Resolve each `discover:` value once, here, and\nreuse it below.\n\nWith `Scheme: none`, skip every step marked **(release)**.\n\n## 1. Preconditions — stop if any fail\n\n- **Not on `main`.** Work happens on a branch. On `main`, stop and offer to create one named by the\n  `Issue link` branch pattern (`\u003Ctype>\u002F\u003Cslug>` when it is `none`).\n- **Clean tree.** `git status --porcelain` prints nothing but the settings files step 0 just wrote,\n  which go into this run's commit. Otherwise stop and ask whether to commit what is there; never\n  commit it silently. Once answered, restart from this step. Every change staged later was then\n  made by this run.\n- **GitHub reachable.** `gh auth status` succeeds, or GitHub MCP can reach this repository.\n- **Companion in step.** When the `Private companion` is set and its checkout exists, run the\n  `Workspace status command`: the companion must be clean and neither ahead of nor behind its\n  upstream. An absent checkout is a valid state; report it.\n- **Up to date with `main`.**\n\n  ```bash\n  git fetch -q --tags origin\n  git merge-base --is-ancestor origin\u002Fmain HEAD && echo current || echo behind\n  ```\n\n  When behind, offer to `git merge origin\u002Fmain` now, and resolve conflicts with the user. Never\n  rebase a pushed branch.\n\nUse `origin\u002Fmain` throughout, never local `main`: a stale local `main` silently widens the diff to\nwork already merged, and a clone that fetched only this branch has none.\n\n## 2. Evaluate the release impact (release)\n\nRead the whole branch, not its latest commit:\n\n```bash\nbase=\"$(git merge-base origin\u002Fmain HEAD)\"\ngit diff --stat \"$base\"..HEAD\ngit log --format='%s%n%b' \"$base\"..HEAD\ngit diff \"$base\"..HEAD\n```\n\nThe stat and the log are an index. Read the diff, and the tests and docs it touches, before\ndeciding. Classify the impact to **this project**, highest level present:\n\n- **Major** — an existing public behavior, API, URL, persisted-data shape, configuration,\n  deployment contract or established user workflow becomes incompatible, and its users must\n  migrate. On a `0.y` line, an incompatible change is minor unless the branch deliberately cuts\n  `1.0.0`.\n- **Minor** — a backwards-compatible capability or a material expansion of behavior, or a\n  deliberate platform or toolchain generation change that raises the supported baseline.\n- **Build** — fixes (security fixes included), dependency maintenance, refactors, tests, docs,\n  tooling: nothing that adds capability or raises a baseline.\n\nJudge this project's contracts, not a dependency's version number. Release metadata and generated\nmirrors are not evidence. With `Scheme: per-merge`, the cumulative content of `Unreleased` counts\ntoo. A level the user asked for is still evaluated; when the evaluation differs, show both and ask.\n\nRecord `Release level: \u003Cmajor|minor|build> — \u003Cone-sentence rationale>`. Steps 9 and 10 use that\nexact line.\n\n**Apply it.** The baseline is the higher of the newest three-part `v*` tag (ignoring the\n`Skipped tags` **Ignore** patterns) and the `Version file` on `origin\u002Fmain` (`git show \"origin\u002Fmain:\u003Cfile>\"`).\n\n- **Build** — the `Version file` stays at its `origin\u002Fmain` value. Restore it if the branch moved it\n  without release intent.\n- **Minor** — the target line is `\u003Cmajor>.\u003Cminor + 1>.0` of the baseline.\n- **Major** — the target line is `\u003Cmajor + 1>.0.0`.\n\nFor major or minor, follow `Ask before bumping` first, then run `Bump command` with the exact\ntarget, so a re-run lands on the same value instead of advancing twice. Check that the version file\nand any lockfile beside it agree. A branch that already carries the target keeps it; a branch that\ncarries a different line was bumped on purpose: ask before replacing it.\n\n## 3. Compute the target version (release)\n\n- **`per-merge`** — first confirm the newest merge on `origin\u002Fmain` is tagged:\n\n  ```bash\n  git tag --points-at origin\u002Fmain -l 'v*'\n  ```\n\n  Empty output means the tag workflow has not finished for a merge that just landed, and the next\n  version would repeat a taken number. Wait for the workflow, fetch tags again, and re-check; if it\n  stays untagged after the workflow finished, ask the user. Then run `Next-version command`. It\n  prints a bare SemVer and is the single source of truth: never compute the build number yourself.\n\n  Check whether another open PR already claims that version. `gh pr diff` takes no path, so cut\n  the `CHANGELOG.md` part out of each diff:\n\n  ```bash\n  branch=\"$(git branch --show-current)\"\n  gh pr list --state open --json number,headRefName --jq '.[] | \"\\(.number) \\(.headRefName)\"' |\n    while read -r number head; do\n      [ \"$head\" = \"$branch\" ] && continue\n      gh pr diff \"$number\" | sed -n '\u002F^diff --git a\\\u002FCHANGELOG.md \u002F,\u002F^diff --git\u002Fp' |\n        grep '^+## \\[' | sed \"s\u002F^\u002F#$number \u002F\"\n    done\n  ```\n\n  If one does, name it in the report: whichever merges second renumbers on its next `ship`.\n- **`cut-on-line`** — a build has no exact target: the next tag assigns it, whether a workflow tags\n  each merge or a maintainer tags a release, and another merge can land first. A confirmed major or\n  minor's target is the new line from step 2.\n\n## 4. Skipped tags (release)\n\nOnly with `Scheme: per-merge` and `Skipped tags` `backfill` or `roll up`. A skipped tag is a merge\nthat wrote no section — a dependency bot's PR, or one opened in the web UI. List them; run the\ncommands exactly, since tags print as `v1.1.5` and sections as `1.1.5`, and comparing raw lists by\neye reports every tag as missing.\n\n- **`backfill`** — every released version with no section:\n\n  ```bash\n  comm -23 \\\n    \u003C(git tag -l 'v*' | sed -nE 's\u002F^v([0-9]+\\.[0-9]+\\.[0-9]+)$\u002F\\1\u002Fp' | sort) \\\n    \u003C(sed -nE 's\u002F^## \\[([0-9]+\\.[0-9]+\\.[0-9]+)\\].*\u002F\\1\u002Fp' CHANGELOG.md | sort)\n  ```\n\n- **`roll up`** — only the versions released after the newest section on `origin\u002Fmain`; older\n  ones were rolled into an earlier section:\n\n  ```bash\n  newest=\"$(git show origin\u002Fmain:CHANGELOG.md |\n    sed -nE 's\u002F^## \\[([0-9]+\\.[0-9]+\\.[0-9]+)\\].*\u002F\\1\u002Fp' | sort -V | tail -1)\"\n  git tag -l 'v*' | sed -nE 's\u002F^v([0-9]+\\.[0-9]+\\.[0-9]+)$\u002F\\1\u002Fp' | sort -V |\n    sed -n \"\u002F^${newest}\\$\u002F,\\$p\" | tail -n +2\n  ```\n\nDrop versions matching the **Ignore** patterns. With `version` set to each one left, read the tag;\nit is the merge commit, so the merged branch is its second parent:\n\n```bash\ngit log -1 --format='%cs' \"v$version\"                  # the section's date\ngit log --format='%s%n%b' \"v$version^1..v$version^2\"   # what landed\ngit diff \"v$version^1\" \"v$version\" --stat              # manifests and lockfiles it changed\ngit log -1 --format=%an \"v$version^2\"                  # dependabot[bot] for a bot PR\n```\n\nKeep it factual: name the packages and versions, and call a lockfile-only change transitive.\nAttribute to a bot only when the second parent's author is the bot: the merge commit's author is\nwhoever clicked Merge. When `^2` does not exist (a squash or fast-forward), read the tag's own\ncommit.\n\n- **`backfill`** — add a dated section for each version in place, newest first.\n- **`roll up`** — invent no section; step 7 writes their changes into this branch's section.\n\n## 5. Refresh the docs\n\nRun the `docs-updater` skill in `fix` mode, scoped to this branch's diff, not a full audit — in a\nsubagent where the harness has one, told to follow `.agents\u002Fskills\u002Fdocs-updater\u002FSKILL.md`;\notherwise follow it yourself. A subagent cannot ask the user, so complete its settings first, here,\nby following its step 0.\n\n```bash\nrange=\"$(git merge-base origin\u002Fmain HEAD)..HEAD\"\n```\n\nTell it what changed and why, that it was invoked by `ship` on an unmerged branch, and that this\nskill writes the changelog and the `Version file`. It leaves its edits uncommitted and returns the\nhuman actions it found for step 6, and any wiki search it owes after the merge (the\n`Follow-up wiki`, or a `Doc map` item in a wiki).\nCompanion edits are committed there as its own repository, never in this one: run the\n`## Procedure` in `.agents\u002Fskills\u002Fship\u002Fsettings\u002Fworkspace.md`.\n\n## 6. Human follow-ups\n\nRun the `## Procedure` in `.agents\u002Fskills\u002Fship\u002Fsettings\u002Fhuman-follow-up.md` for every required human\naction this branch leaves, before the PR opens, including those `docs-updater` returned. Reconcile\nrather than duplicate; on a re-ship, reuse the records already made. A follow-up never lives only\nin the changelog or the PR body. Its links go in the report and private records, never in the\npublic PR.\n\n## 7. Write the changelog (release)\n\nWrite user-visible behavior and its consequences, derived from the diff — not a commit log. Use the\nheadings the file already uses (Keep a Changelog: `Added`, `Changed`, `Deprecated`, `Removed`,\n`Fixed`, `Security`, plus any the file adds), one of each per section, and match its voice. Dates\nare today's, `YYYY-MM-DD`.\n\n**Idempotent.** List the sections this branch added:\n\n```bash\ngit diff origin\u002Fmain...HEAD -- CHANGELOG.md | grep '^+## \\['\n```\n\nA section listed there is this branch's from an earlier `ship`: rewrite it in place, never stack a\nsecond. Entries this branch added to `Unreleased` are rewritten the same way.\n\n- **`per-merge`** — insert `## [\u003Ctarget>] - \u003Cdate>` directly below `## [Unreleased]`, holding this\n  branch's entries plus anything accumulated in `Unreleased` and, with `roll up`, the changes of\n  the tags step 4 listed; reset `Unreleased` to the\n  `Unreleased placeholder`. When the branch's section names an older version because another PR merged first,\n  **renumber that section** to the target. Then merge `origin\u002Fmain`: their section sits in the same\n  place, so resolve `CHANGELOG.md` keeping both, newest version first, and go back to step 3 — their\n  merge minted a tag, so the target moved again.\n- **`cut-on-line`, build** — add the entries under `Unreleased`, replacing its placeholder. No dated\n  section, no `Version file` edit.\n- **`cut-on-line`, confirmed major or minor** — add the entries under `Unreleased`, move its whole\n  content into `## [\u003Ctarget>] - \u003Cdate>`, and restore the placeholder. When the cut is already there\n  from an earlier `ship`, rewrite this branch's entries inside it; never leave them both above and\n  below the cut.\n\n**Reference links.** When the file ends in a link footer, keep it consistent in the pattern its\nentries follow: `[Unreleased]` compares from the newest version to `HEAD`, and each new or\nrenumbered section — backfilled ones too — gets its own link, newest first.\n\nRun `Changelog check`. A mismatch names the version the merge will really mint: redo this step with\nit.\n\n## 8. Fast checks — refuse to push if any fail\n\nRun every `Fast checks` entry, in order, from its folder; skip a conditional entry only when none of\nits paths changed (`git diff --name-only origin\u002Fmain...HEAD`). They run after the doc and changelog\nedits, because formatters and linters cover those files too.\n\nIf any is red, stop and report; do not push. Offer the entry's fix command. After a fix that writes\nfiles, run the list again from the top: a generated mirror built from unformatted sources is stale\nagain once they are formatted. A check that cannot run here (a missing service, a missing secret) is\nnamed in the report as left to CI.\n\nThen run `Hook: before PR` from `docs\u002Fagents\u002Fship.md`. Its findings go in the report and, where it\nsays, the PR body.\n\n## 9. Commit, push, and open or update the PR\n\nCommit only when `git status --porcelain` shows changes; a re-ship with nothing new makes no empty\ncommit. Staging everything is safe because step 1 proved the tree was clean, and the companion is\nignored, never staged:\n\n```bash\ngit add -A\ngit commit -m \"\u003CRelease commit message, with the real version>\"\ngit push -u origin \"$(git branch --show-current)\"\n```\n\nA rejected push means the remote has commits this checkout lacks: stop and report. Never force-push.\n\n```bash\ngh pr list --head \"$(git branch --show-current)\" --state open --json number,url\n```\n\n- **No PR** → `gh pr create --base main`.\n- **A PR exists** → `gh pr edit \u003Cnumber>` to refresh its body. Never open a second PR.\n\nWrite the body to a temporary file and pass `--body-file`. Fill the repository's PR template\n(`.github\u002Fpull_request_template.md` or `PULL_REQUEST_TEMPLATE.md`) when there is one, from the\nchangelog entries and the diff. Tick a checkbox only on evidence from the diff, the fast checks or\n`Hook: before PR`, and leave the rest unticked; where the template asks how the change was\nverified, name the fast checks actually run and the checks left to CI. Include the\n`Release level:` line from step 2 and, with `per-merge`, the version this merge will mint.\n\n**Issue link**, when the setting is not `none`. The body opens with the link line, in the slot the\ntemplate leaves for it:\n\n- Take `N` from the branch per its **Branch pattern**, and read the issue:\n  `gh issue view \u003CN> --json title,state,labels,body`.\n- The finishing line (`Closes #N`) when this PR finishes the issue; the slice line (`Part of #N`)\n  when it is one slice of a spec that stays open. Each finished issue gets its own keyword:\n  GitHub links only the first issue in `Closes #1 and #2`.\n- A branch with no number: the **Waiver line** when the user waived the flow; no link line for an\n  **Exempt** kind, or for work from a ready issue in the `Private issue repository`.\n- When the branch's number and the issue disagree, or finishing versus slice is unclear, ask before\n  creating the PR. A refreshed body keeps its link line. A number in the title alone links nothing.\n\nWarn, never block, when the PR opens with no link line and neither of those applies, or when the\n`Board` is set and the linked issue is not on it. An issue in the `Private issue repository` is never named in a\npublic PR body, commit message or public issue; it is closed by hand after the merge.\n\nNothing this step writes in public carries a private repository name, link, board number or\ncompanion detail.\n\n## 10. Report\n\n- The PR URL and branch.\n- The `Release level:` line and its evidence; the version this merge will mint (`per-merge`), the\n  new line (a `cut-on-line` cut), or that the next tag assigns the build. Name a competing PR\n  claiming the same version, and say the section is renumbered on a re-ship.\n- What the docs refresh changed, the changelog entries written, and any sections backfilled. When\n  docs-updater owes a wiki search after the merge, say so: the next `end-session` performs it.\n- Human follow-ups: verified issue and wiki links, what is unpublished and why, or that none remain.\n- Fast-check results, checks left to CI, `Hook: before PR` findings, and issue-link warnings.\n- The companion: absent, or clean and in step, and any companion commit made. Never describe the\n  unmerged PR as shipped there.\n- Settings files written in step 0.\n\nSay plainly that the full suites run in CI, not here: the branch is verified only as far as the fast\nchecks go.\n",{"name":5,"metadata":24,"description":7},{"settings":25},"workspace issue-tracker human-follow-up releases ship dev-flow triage-labels agents-md","main","ef2223ea7bc420ae5a16e329c8c6d952dba61654",".agents\u002Fskills\u002Fship","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset","https:\u002F\u002Fgithub.com\u002Fjwh3times","2026-11-15 04:07:44",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add jwh3times\u002Fcauset --skill ship",{"tool":38,"command":39},"bunx","bunx skills add jwh3times\u002Fcauset --skill ship",{"tool":41,"command":42},"pnpm","pnpm dlx skills add jwh3times\u002Fcauset --skill ship","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"settings\u002Fagents-md.md","REFERENCE","参考文档",5301,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship\u002Fsettings\u002Fagents-md.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"settings\u002Fdev-flow.md",5438,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship\u002Fsettings\u002Fdev-flow.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"settings\u002Fhuman-follow-up.md",6331,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship\u002Fsettings\u002Fhuman-follow-up.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"settings\u002Fissue-tracker.md",4028,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship\u002Fsettings\u002Fissue-tracker.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"settings\u002FREADME.md",3227,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship\u002Fsettings\u002FREADME.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"settings\u002Freleases.md",6085,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship\u002Fsettings\u002Freleases.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"settings\u002Fship.md",2930,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship\u002Fsettings\u002Fship.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"settings\u002Ftriage-labels.md",1236,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship\u002Fsettings\u002Ftriage-labels.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"settings\u002Fworkspace.md",7151,"https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship\u002Fsettings\u002Fworkspace.md",[85,92,99,106,113,120],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7B3THV5B9P8M96HAW1J6PZY","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7B3TERY71JK36VZ1VX542A9","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7B3TAJBRTRZEB0FV1YCHBWC","what-next","Report what to work on next in this repository — an active handoff waiting to be resumed, work already in flight, ready issues ranked the way the board ranks them, what needs the user, what needs shaping first, and blocks that have quietly cleared — and recommend the one command to run. Read-only. Use when the user asks what to work on next, what is ready or what to pick up, or when a phase ends with no next piece of work chosen.","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwhat-next\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7B3T6XH8Q9A1NQGP1QZ1T3N","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7B3T4R32FFJHX3HKFK2F46C","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7B3T27A99CF7MBH5CAPTZPW","triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fjwh3times\u002Fcauset\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriage\u002FSKILL.md",[],[]]