[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77QZ2CVF0FPVS73TRNBZ09N":3,"skill-same:01M77QZ2CVF0FPVS73TRNBZ09N":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M77QZ2CVF0FPVS73TRNBZ09N","release-next-version",null,"Ship the current branch as the next Perch release. Opens (or reuses) a PR for the current branch, waits for the PR checks, stops and reports a FAIL if any check fails, otherwise squash-merges it, then tags the new main head with the csproj version (vX.Y.Z) and pushes the tag, which kicks off the Release workflow — and watches that workflow until the GitHub Release is published or the build fails. Use when the user says \"release next version\", \"release this\", \"\u002Frelease-next-version\", or wants to merge the current branch and cut the tagged release.","ArcticGizmo\u002Fperch","ArcticGizmo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F18655632?v=4","01M77QYSY2QBAG1YK4V6TZ4HV4","Jonathan Howell","01M77QYSZ6NYN7W76H7QAMDPEE",2,"MIT","https:\u002F\u002Fgithub.com\u002FArcticGizmo\u002Fperch\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease-next-version\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: release-next-version\ndescription: Ship the current branch as the next Perch release. Opens (or reuses) a PR for the current branch, waits for the PR checks, stops and reports a FAIL if any check fails, otherwise squash-merges it, then tags the new main head with the csproj version (vX.Y.Z) and pushes the tag, which kicks off the Release workflow — and watches that workflow until the GitHub Release is published or the build fails. Use when the user says \"release next version\", \"release this\", \"\u002Frelease-next-version\", or wants to merge the current branch and cut the tagged release.\n---\n\n# Release Next Version\n\nTakes the current branch from \"done\" to \"published release\": PR → green checks → squash-merge → tag the\nnew `main` head → push the tag → watch the Release workflow to completion. Pushing a `v*` tag triggers\n`.github\u002Fworkflows\u002Frelease.yml`, which builds and publishes the GitHub Release.\n\nInvoking this skill is the user's go-ahead for the outward-facing steps (pushing the branch, opening the\nPR, merging, pushing the tag). Anything *not* listed here (force-pushes, bypassing checks, deleting\nbranches, re-tagging) is out of scope — stop and ask.\n\n## Repo facts this relies on\n\n- Repo is `ArcticGizmo\u002Fperch`; **squash-merge only** (merge commits and rebase are disabled) and the\n  remote branch is auto-deleted on merge.\n- Tags are **lightweight**, `vMAJOR.MINOR.PATCH`, and must match `\u003CVersion>` in\n  `src\u002FPerch.App\u002FPerch.App.csproj` (the release build takes its version from the tag).\n- CI (`ci.yml`) runs on pull requests only, and is skipped by `paths-ignore` when a PR only touches\n  root `*.md`, `docs\u002F**`, `captures\u002F**` or `backend\u002F**` — so a PR can legitimately have **no checks**.\n- The Release workflow (`release.yml`) has three jobs: `build-windows` and `build-macos` run in parallel,\n  then `release` (`needs` both) is the **only** job that creates the GitHub Release. A failed build means\n  no Release is published at all — never a half-populated one. A tag-triggered run's `headBranch` is the\n  tag name (e.g. `v0.5.23`). The jobs set no `timeout-minutes`, so GitHub's 6-hour default applies; a\n  healthy run takes roughly 10–20 minutes.\n- Use the Bash tool (Git Bash) for the snippets below.\n\n## Steps\n\n### 1. Preflight — gather everything in one batch\n\n```bash\nBRANCH=$(git rev-parse --abbrev-ref HEAD); echo \"BRANCH=$BRANCH\"\necho \"=== status ===\"; git status --porcelain\ngit fetch origin --tags --quiet\nVERSION=$(sed -n 's\u002F.*\u003CVersion>\\(.*\\)\u003C\\\u002FVersion>.*\u002F\\1\u002Fp' src\u002FPerch.App\u002FPerch.App.csproj | head -1); echo \"VERSION=$VERSION\"\necho \"LAST_TAG=$(git tag --sort=-v:refname | head -1)\"\necho \"TAG_EXISTS_LOCAL=$(git tag -l \"v$VERSION\")\"\necho \"TAG_EXISTS_REMOTE=$(git ls-remote --tags origin \"refs\u002Ftags\u002Fv$VERSION\")\"\necho \"=== commits on $BRANCH not on origin\u002Fmain ===\"\ngit log origin\u002Fmain..HEAD --no-merges --pretty=format:'%h %s'\necho; echo \"=== existing PR ===\"; gh pr view --json number,state,url,title 2>&1\n```\n\nStop and report (don't try to fix it yourself) if any of these hold:\n\n- `BRANCH` is `main` (or detached `HEAD`) — there's nothing to PR. Say so.\n- The working tree is dirty — uncommitted changes wouldn't be in the release. List them and ask\n  whether to commit them first.\n- There are no commits on the branch ahead of `origin\u002Fmain`.\n- `v$VERSION` already exists (locally or on the remote), or `VERSION` isn't greater than `LAST_TAG` —\n  the version hasn't been bumped. Suggest running `\u002Fbump-version` (and committing its csproj +\n  `CHANGELOG.md` edits) first. Never move or overwrite an existing tag.\n- An existing PR for the branch is `CLOSED` or `MERGED` — ask rather than open a second one.\n\n### 2. Push the branch and open (or reuse) the PR\n\n```bash\ngit push -u origin HEAD\n```\n\nIf step 1 found an `OPEN` PR, reuse it. Otherwise create one against `main`:\n\n- **Title:** a concise summary of the branch's net change (if the branch is a single feature, its name;\n  otherwise the headline items), ending with `; bump to $VERSION` when the branch carries the bump —\n  matching history, e.g. `Composer: mid-prompt skills, [Image #N] markers, popup repaint fix; bump to 0.5.18`.\n- **Body:** a short `## Summary` of the user-facing changes (from the commit list in step 1 and, if\n  present, the new `## [v$VERSION]` section in `CHANGELOG.md`), a `## Test plan` noting what CI covers\n  and anything still unverified live, then the PR attribution line.\n\nWrite the body to a temp file and pass it with `--body-file` (avoids quoting trouble):\n\n```bash\ngh pr create --base main --head \"$BRANCH\" --title \"\u003Ctitle>\" --body-file \u003Cfile>\n```\n\nRecord the PR number and URL.\n\n### 3. Wait for the checks\n\nCI takes several minutes (each job has a 30-minute ceiling), so run the wait with the Bash tool's\n`run_in_background: true` and a timeout of about 45 minutes (`2700000` ms), then wait for the\ncompletion notification — don't poll. Checks can take a few seconds to register after the PR opens,\nhence the short lead-in loop:\n\n```bash\nPR=\u003Cnumber>\nfound=0\nfor i in $(seq 1 18); do\n  if gh pr checks \"$PR\" 2>&1 | grep -q 'no checks reported'; then sleep 10; else found=1; break; fi\ndone\nif [ \"$found\" = 0 ]; then echo \"RESULT=NO_CHECKS\"; exit 0; fi\ngh pr checks \"$PR\" --watch --fail-fast --interval 30\necho \"RESULT=EXIT_$?\"\n```\n\nThen branch on the result:\n\n- **`EXIT_0`** — all checks passed. Continue to step 4.\n- **Any other exit** — a check failed (or was cancelled). **Stop: this is a FAIL that needs fixing.**\n  Do not merge, do not tag. Gather the evidence:\n\n  ```bash\n  gh pr checks \"$PR\"\n  gh run list --branch \"$BRANCH\" --workflow ci.yml --limit 1 --json databaseId,url,conclusion\n  gh run view \u003CdatabaseId> --log-failed | tail -80\n  ```\n\n  Report back headed **`RELEASE FAILED — checks did not pass`**, with the PR URL, which job\u002Fstep failed,\n  the run URL, and the relevant tail of the failed log (the failing test names \u002F compiler errors). Leave\n  the PR open. Don't attempt a fix unless the user asks.\n- **`NO_CHECKS`** — nothing ran. Usually that's `paths-ignore` (docs\u002Fmarkdown-only PR); say so, and ask\n  the user whether to merge without checks. Don't merge on your own.\n\n### 4. Squash-merge\n\n```bash\ngh pr merge \"$PR\" --squash\n```\n\nDon't pass `--delete-branch` (the remote branch is auto-deleted; leave the local branch alone — after a\nsquash it can only be force-deleted, which is the user's call). Don't pass `--admin` or `--auto`. If the\nmerge is refused (required review, branch protection, merge conflict), stop and report the message.\n\nThen confirm the merge and capture the squash commit:\n\n```bash\ngh pr view \"$PR\" --json state,mergeCommit -q '.state + \" \" + .mergeCommit.oid'\ngit fetch origin --tags --quiet\ngit checkout main && git pull --ff-only origin main\necho \"MAIN_HEAD=$(git rev-parse HEAD)\"\n```\n\n`state` must be `MERGED`. Normally `MAIN_HEAD` equals the merge commit. If it doesn't, something else\nlanded on `main` in the meantime — stop and ask which commit to tag rather than guessing.\n\nIf `git pull --ff-only` fails (local `main` had diverged), stop and report — don't reset it.\n\n### 5. Tag the new main head and push the tag\n\n```bash\ngit tag \"v$VERSION\" \"$MAIN_HEAD\"\ngit push origin \"v$VERSION\"\n```\n\n(Lightweight tag, matching the existing ones.) Then find the Release run the tag triggered, filtering on\nthe tag so a stale or concurrent run can't be picked up. It can take a few seconds to register:\n\n```bash\nRUN=\"\"\nfor i in $(seq 1 24); do\n  RUN=$(gh run list --workflow release.yml --branch \"v$VERSION\" --event push --limit 1 --json databaseId -q '.[0].databaseId')\n  [ -n \"$RUN\" ] && break\n  sleep 5\ndone\necho \"RUN=$RUN\"\n[ -n \"$RUN\" ] && gh run view \"$RUN\" --json url -q .url\n```\n\nIf `RUN` is still empty after ~2 minutes, stop and report: the tag is pushed but no Release run started\n(check the Actions tab — the workflow may be disabled). Don't re-push or re-tag.\n\n### 6. Watch the Release workflow\n\nA healthy run takes 10–20 minutes, so run the watch with the Bash tool's `run_in_background: true` and a\ntimeout of 60 minutes (`3600000` ms), then wait for the completion notification — don't poll. The watch\noutput is redirected because `gh run watch` redraws the whole job table every interval; the summary after\nit is what you read:\n\n```bash\nRUN=\u003Cid>\ngh run watch \"$RUN\" --exit-status --interval 30 > \u002Fdev\u002Fnull 2>&1\necho \"RESULT=EXIT_$?\"\ngh run view \"$RUN\" --json status,conclusion,url,jobs \\\n  -q '\"run: \" + .status + \" \" + (.conclusion \u002F\u002F \"-\") + \"  \" + .url, (.jobs[] | \"  \" + .name + \": \" + .status + \" \" + (.conclusion \u002F\u002F \"-\"))'\n```\n\nThen branch on the result:\n\n- **`EXIT_0`** — the run succeeded. Confirm the Release really exists with the assets the install path\n  depends on:\n\n  ```bash\n  gh release view \"v$VERSION\" --json url,isDraft,assets \\\n    -q '.url, (\"draft: \" + (.isDraft|tostring)), (.assets[] | \"  \" + .name)'\n  ```\n\n  `Perch-win-Setup.exe` and `SHA256SUMS.txt` must both be listed (`install.ps1` resolves the first and\n  verifies it against the second). If either is missing, or the Release is a draft, report it as a\n  problem — the run went green but the one-liner installer can't use this release.\n- **Any other exit** — a job failed or was cancelled. **Stop: this is a RELEASE BUILD FAILURE.** The tag is\n  pushed but, because `release` needs both builds, **no GitHub Release was published**. Gather the evidence:\n\n  ```bash\n  gh run view \"$RUN\" --log-failed | tail -80\n  ```\n\n  Report back headed **`RELEASE BUILD FAILED — v$VERSION tagged, no Release published`**, with the run URL,\n  which job\u002Fstep failed, and the relevant tail of the failed log. Don't re-run, re-tag, delete the tag or\n  push a fix on your own — say that the usual recovery once the cause is understood is\n  `gh run rerun \"$RUN\" --failed` (a flaky runner) or a fix plus a new patch version (a real break), and\n  let the user choose.\n- **The background task timed out** (no `RESULT` line after 60 minutes) — the run is still going or stuck.\n  Report the run URL and the current job statuses (the `gh run view` line above), and don't wait further\n  unless asked.\n\n### 7. Report back\n\nPrint, plainly:\n\n- **`Released v$VERSION`**\n- The PR URL (merged) and the squash commit SHA that was tagged.\n- The Release workflow run URL and its outcome (all three jobs green).\n- The GitHub Release URL and confirmation that `Perch-win-Setup.exe` and `SHA256SUMS.txt` are attached.\n- That local `main` is checked out and up to date, and the local branch `$BRANCH` still exists (the\n  remote one was auto-deleted).\n\nOn any stop in steps 1–6, report exactly which step stopped, why, and what state things were left in\n(e.g. \"PR #57 open, not merged, no tag\", or \"PR #57 merged, v0.5.18 tagged, Release build failed on\nbuild-macos — no Release published\").\n","# Release Next Version\n\nTakes the current branch from \"done\" to \"published release\": PR → green checks → squash-merge → tag the\nnew `main` head → push the tag → watch the Release workflow to completion. Pushing a `v*` tag triggers\n`.github\u002Fworkflows\u002Frelease.yml`, which builds and publishes the GitHub Release.\n\nInvoking this skill is the user's go-ahead for the outward-facing steps (pushing the branch, opening the\nPR, merging, pushing the tag). Anything *not* listed here (force-pushes, bypassing checks, deleting\nbranches, re-tagging) is out of scope — stop and ask.\n\n## Repo facts this relies on\n\n- Repo is `ArcticGizmo\u002Fperch`; **squash-merge only** (merge commits and rebase are disabled) and the\n  remote branch is auto-deleted on merge.\n- Tags are **lightweight**, `vMAJOR.MINOR.PATCH`, and must match `\u003CVersion>` in\n  `src\u002FPerch.App\u002FPerch.App.csproj` (the release build takes its version from the tag).\n- CI (`ci.yml`) runs on pull requests only, and is skipped by `paths-ignore` when a PR only touches\n  root `*.md`, `docs\u002F**`, `captures\u002F**` or `backend\u002F**` — so a PR can legitimately have **no checks**.\n- The Release workflow (`release.yml`) has three jobs: `build-windows` and `build-macos` run in parallel,\n  then `release` (`needs` both) is the **only** job that creates the GitHub Release. A failed build means\n  no Release is published at all — never a half-populated one. A tag-triggered run's `headBranch` is the\n  tag name (e.g. `v0.5.23`). The jobs set no `timeout-minutes`, so GitHub's 6-hour default applies; a\n  healthy run takes roughly 10–20 minutes.\n- Use the Bash tool (Git Bash) for the snippets below.\n\n## Steps\n\n### 1. Preflight — gather everything in one batch\n\n```bash\nBRANCH=$(git rev-parse --abbrev-ref HEAD); echo \"BRANCH=$BRANCH\"\necho \"=== status ===\"; git status --porcelain\ngit fetch origin --tags --quiet\nVERSION=$(sed -n 's\u002F.*\u003CVersion>\\(.*\\)\u003C\\\u002FVersion>.*\u002F\\1\u002Fp' src\u002FPerch.App\u002FPerch.App.csproj | head -1); echo \"VERSION=$VERSION\"\necho \"LAST_TAG=$(git tag --sort=-v:refname | head -1)\"\necho \"TAG_EXISTS_LOCAL=$(git tag -l \"v$VERSION\")\"\necho \"TAG_EXISTS_REMOTE=$(git ls-remote --tags origin \"refs\u002Ftags\u002Fv$VERSION\")\"\necho \"=== commits on $BRANCH not on origin\u002Fmain ===\"\ngit log origin\u002Fmain..HEAD --no-merges --pretty=format:'%h %s'\necho; echo \"=== existing PR ===\"; gh pr view --json number,state,url,title 2>&1\n```\n\nStop and report (don't try to fix it yourself) if any of these hold:\n\n- `BRANCH` is `main` (or detached `HEAD`) — there's nothing to PR. Say so.\n- The working tree is dirty — uncommitted changes wouldn't be in the release. List them and ask\n  whether to commit them first.\n- There are no commits on the branch ahead of `origin\u002Fmain`.\n- `v$VERSION` already exists (locally or on the remote), or `VERSION` isn't greater than `LAST_TAG` —\n  the version hasn't been bumped. Suggest running `\u002Fbump-version` (and committing its csproj +\n  `CHANGELOG.md` edits) first. Never move or overwrite an existing tag.\n- An existing PR for the branch is `CLOSED` or `MERGED` — ask rather than open a second one.\n\n### 2. Push the branch and open (or reuse) the PR\n\n```bash\ngit push -u origin HEAD\n```\n\nIf step 1 found an `OPEN` PR, reuse it. Otherwise create one against `main`:\n\n- **Title:** a concise summary of the branch's net change (if the branch is a single feature, its name;\n  otherwise the headline items), ending with `; bump to $VERSION` when the branch carries the bump —\n  matching history, e.g. `Composer: mid-prompt skills, [Image #N] markers, popup repaint fix; bump to 0.5.18`.\n- **Body:** a short `## Summary` of the user-facing changes (from the commit list in step 1 and, if\n  present, the new `## [v$VERSION]` section in `CHANGELOG.md`), a `## Test plan` noting what CI covers\n  and anything still unverified live, then the PR attribution line.\n\nWrite the body to a temp file and pass it with `--body-file` (avoids quoting trouble):\n\n```bash\ngh pr create --base main --head \"$BRANCH\" --title \"\u003Ctitle>\" --body-file \u003Cfile>\n```\n\nRecord the PR number and URL.\n\n### 3. Wait for the checks\n\nCI takes several minutes (each job has a 30-minute ceiling), so run the wait with the Bash tool's\n`run_in_background: true` and a timeout of about 45 minutes (`2700000` ms), then wait for the\ncompletion notification — don't poll. Checks can take a few seconds to register after the PR opens,\nhence the short lead-in loop:\n\n```bash\nPR=\u003Cnumber>\nfound=0\nfor i in $(seq 1 18); do\n  if gh pr checks \"$PR\" 2>&1 | grep -q 'no checks reported'; then sleep 10; else found=1; break; fi\ndone\nif [ \"$found\" = 0 ]; then echo \"RESULT=NO_CHECKS\"; exit 0; fi\ngh pr checks \"$PR\" --watch --fail-fast --interval 30\necho \"RESULT=EXIT_$?\"\n```\n\nThen branch on the result:\n\n- **`EXIT_0`** — all checks passed. Continue to step 4.\n- **Any other exit** — a check failed (or was cancelled). **Stop: this is a FAIL that needs fixing.**\n  Do not merge, do not tag. Gather the evidence:\n\n  ```bash\n  gh pr checks \"$PR\"\n  gh run list --branch \"$BRANCH\" --workflow ci.yml --limit 1 --json databaseId,url,conclusion\n  gh run view \u003CdatabaseId> --log-failed | tail -80\n  ```\n\n  Report back headed **`RELEASE FAILED — checks did not pass`**, with the PR URL, which job\u002Fstep failed,\n  the run URL, and the relevant tail of the failed log (the failing test names \u002F compiler errors). Leave\n  the PR open. Don't attempt a fix unless the user asks.\n- **`NO_CHECKS`** — nothing ran. Usually that's `paths-ignore` (docs\u002Fmarkdown-only PR); say so, and ask\n  the user whether to merge without checks. Don't merge on your own.\n\n### 4. Squash-merge\n\n```bash\ngh pr merge \"$PR\" --squash\n```\n\nDon't pass `--delete-branch` (the remote branch is auto-deleted; leave the local branch alone — after a\nsquash it can only be force-deleted, which is the user's call). Don't pass `--admin` or `--auto`. If the\nmerge is refused (required review, branch protection, merge conflict), stop and report the message.\n\nThen confirm the merge and capture the squash commit:\n\n```bash\ngh pr view \"$PR\" --json state,mergeCommit -q '.state + \" \" + .mergeCommit.oid'\ngit fetch origin --tags --quiet\ngit checkout main && git pull --ff-only origin main\necho \"MAIN_HEAD=$(git rev-parse HEAD)\"\n```\n\n`state` must be `MERGED`. Normally `MAIN_HEAD` equals the merge commit. If it doesn't, something else\nlanded on `main` in the meantime — stop and ask which commit to tag rather than guessing.\n\nIf `git pull --ff-only` fails (local `main` had diverged), stop and report — don't reset it.\n\n### 5. Tag the new main head and push the tag\n\n```bash\ngit tag \"v$VERSION\" \"$MAIN_HEAD\"\ngit push origin \"v$VERSION\"\n```\n\n(Lightweight tag, matching the existing ones.) Then find the Release run the tag triggered, filtering on\nthe tag so a stale or concurrent run can't be picked up. It can take a few seconds to register:\n\n```bash\nRUN=\"\"\nfor i in $(seq 1 24); do\n  RUN=$(gh run list --workflow release.yml --branch \"v$VERSION\" --event push --limit 1 --json databaseId -q '.[0].databaseId')\n  [ -n \"$RUN\" ] && break\n  sleep 5\ndone\necho \"RUN=$RUN\"\n[ -n \"$RUN\" ] && gh run view \"$RUN\" --json url -q .url\n```\n\nIf `RUN` is still empty after ~2 minutes, stop and report: the tag is pushed but no Release run started\n(check the Actions tab — the workflow may be disabled). Don't re-push or re-tag.\n\n### 6. Watch the Release workflow\n\nA healthy run takes 10–20 minutes, so run the watch with the Bash tool's `run_in_background: true` and a\ntimeout of 60 minutes (`3600000` ms), then wait for the completion notification — don't poll. The watch\noutput is redirected because `gh run watch` redraws the whole job table every interval; the summary after\nit is what you read:\n\n```bash\nRUN=\u003Cid>\ngh run watch \"$RUN\" --exit-status --interval 30 > \u002Fdev\u002Fnull 2>&1\necho \"RESULT=EXIT_$?\"\ngh run view \"$RUN\" --json status,conclusion,url,jobs \\\n  -q '\"run: \" + .status + \" \" + (.conclusion \u002F\u002F \"-\") + \"  \" + .url, (.jobs[] | \"  \" + .name + \": \" + .status + \" \" + (.conclusion \u002F\u002F \"-\"))'\n```\n\nThen branch on the result:\n\n- **`EXIT_0`** — the run succeeded. Confirm the Release really exists with the assets the install path\n  depends on:\n\n  ```bash\n  gh release view \"v$VERSION\" --json url,isDraft,assets \\\n    -q '.url, (\"draft: \" + (.isDraft|tostring)), (.assets[] | \"  \" + .name)'\n  ```\n\n  `Perch-win-Setup.exe` and `SHA256SUMS.txt` must both be listed (`install.ps1` resolves the first and\n  verifies it against the second). If either is missing, or the Release is a draft, report it as a\n  problem — the run went green but the one-liner installer can't use this release.\n- **Any other exit** — a job failed or was cancelled. **Stop: this is a RELEASE BUILD FAILURE.** The tag is\n  pushed but, because `release` needs both builds, **no GitHub Release was published**. Gather the evidence:\n\n  ```bash\n  gh run view \"$RUN\" --log-failed | tail -80\n  ```\n\n  Report back headed **`RELEASE BUILD FAILED — v$VERSION tagged, no Release published`**, with the run URL,\n  which job\u002Fstep failed, and the relevant tail of the failed log. Don't re-run, re-tag, delete the tag or\n  push a fix on your own — say that the usual recovery once the cause is understood is\n  `gh run rerun \"$RUN\" --failed` (a flaky runner) or a fix plus a new patch version (a real break), and\n  let the user choose.\n- **The background task timed out** (no `RESULT` line after 60 minutes) — the run is still going or stuck.\n  Report the run URL and the current job statuses (the `gh run view` line above), and don't wait further\n  unless asked.\n\n### 7. Report back\n\nPrint, plainly:\n\n- **`Released v$VERSION`**\n- The PR URL (merged) and the squash commit SHA that was tagged.\n- The Release workflow run URL and its outcome (all three jobs green).\n- The GitHub Release URL and confirmation that `Perch-win-Setup.exe` and `SHA256SUMS.txt` are attached.\n- That local `main` is checked out and up to date, and the local branch `$BRANCH` still exists (the\n  remote one was auto-deleted).\n\nOn any stop in steps 1–6, report exactly which step stopped, why, and what state things were left in\n(e.g. \"PR #57 open, not merged, no tag\", or \"PR #57 merged, v0.5.18 tagged, Release build failed on\nbuild-macos — no Release published\").\n",{"name":5,"description":7},"main","fea89f2758df190b4aa00e89750d08394c1f4514",".claude\u002Fskills\u002Frelease-next-version","https:\u002F\u002Fgithub.com\u002FArcticGizmo\u002Fperch","https:\u002F\u002Farcticgizmo.github.io\u002Fperch\u002F","https:\u002F\u002Fgithub.com\u002FArcticGizmo","2026-11-13 15:36:44",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add ArcticGizmo\u002Fperch --skill release-next-version",{"tool":37,"command":38},"bunx","bunx skills add ArcticGizmo\u002Fperch --skill release-next-version",{"tool":40,"command":41},"pnpm","pnpm dlx skills add ArcticGizmo\u002Fperch --skill release-next-version","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FArcticGizmo\u002Fperch\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease-next-version\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M77QZHGAVPX56TAK4S778KZ7","demo-skill","A demo user skill used by the SkillCatalog tests.","https:\u002F\u002Fgithub.com\u002FArcticGizmo\u002Fperch\u002Fblob\u002Fmain\u002Ftests\u002FPerch.Tests\u002Ffixtures\u002Fclaude\u002Fskills\u002Fdemo-skill\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77QZF9YSWK4ZFC0WA5HRHGW","context","A skill whose name collides with a built-in and must be excluded.","https:\u002F\u002Fgithub.com\u002FArcticGizmo\u002Fperch\u002Fblob\u002Fmain\u002Ftests\u002FPerch.Tests\u002Ffixtures\u002Fclaude\u002Fskills\u002Fcontext\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77QZDH36FKYC3QPSRVTFB5V","block-skill","First line of a block-scalar description.\nSecond line that should be ignored by the palette.","https:\u002F\u002Fgithub.com\u002FArcticGizmo\u002Fperch\u002Fblob\u002Fmain\u002Ftests\u002FPerch.Tests\u002Ffixtures\u002Fclaude\u002Fskills\u002Fblock-skill\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77QZB49Z4NZY4S3TAYXFFC4","widget","An advertised plugin skill (acme:widget).","https:\u002F\u002Fgithub.com\u002FArcticGizmo\u002Fperch\u002Fblob\u002Fmain\u002Ftests\u002FPerch.Tests\u002Ffixtures\u002Fclaude\u002Fplugins\u002Fmarketplaces\u002Facme\u002Fplugins\u002Facme\u002Fskills\u002Fwidget\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77QZ8NQV6BRXR51CYAB3G1P","gadget","An installed-but-not-advertised plugin skill (must not appear).","https:\u002F\u002Fgithub.com\u002FArcticGizmo\u002Fperch\u002Fblob\u002Fmain\u002Ftests\u002FPerch.Tests\u002Ffixtures\u002Fclaude\u002Fplugins\u002Fmarketplaces\u002Facme\u002Fplugins\u002Facme\u002Fskills\u002Fgadget\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M77QYWN5B5DD8HBCTN3G4639","bump-version","Bump the Perch version and refresh the changelog. Determines the next version from the LAST GIT TAG (not the csproj value, which can drift), bumps src\u002FPerch.App\u002FPerch.App.csproj, backfills changelog sections for any tagged versions that were never documented, summarises every change since the last tag into a new CHANGELOG.md section (keeping the dry humour), clears the Unreleased section, and prints the new version plus its changelog entries. Use when the user says \"bump version\", \"bump the version\", \"\u002Fbump-version\", or wants to cut a new release entry.","https:\u002F\u002Fgithub.com\u002FArcticGizmo\u002Fperch\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbump-version\u002FSKILL.md",[],[]]