Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kansoku-trade/release
Use when the user wants to release a new desktop app version (发版 / release / 发布新版本) — bumps apps/desktop version, writes user-facing release notes into CHANGELOG.md, and opens the release PR that drives the automated tag → build → publish pipeline
Passed 14 of 18 test cases with the skill, and 7 of 18 without it.
and 8 more in the full report
9 fixed8 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are releasing Kansoku desktop without passing an explicit bump type. The commit history since desktop-v1.2.0 includes 'feat(desktop): add indicator toggle switch'. What version bump type should be suggested to the user?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends a minor version increment when new user features are present in recent commits | Passed | Passed |
| Requests user confirmation of the suggested version before editing package files | Missed | Passed |
The instructions your model reads when the skill loads.
Opens a version-bump PR for the Kansoku desktop app. Everything after the PR merge is automated:
this skill → release PR (ci.yml gates it) → merge to main
→ desktop-tag.yml creates desktop-vX.Y.Z + dispatches desktop-release.yml
→ build, sign, appcast, publish GitHub Release (notes from CHANGELOG.md)
→ users receive the Sparkle update
Optional argument: patch | minor | major — skips the bump suggestion step.
git status --porcelain # must be empty
git branch --show-current # must be main
git fetch origin main && git rev-list --count main..origin/main # must be 0
If apps/pro is present (linked worktree), also pin the release to that commit before opening the PR. desktop-release.yml fetches Pro at the GitHub Actions variable KANSOKU_PRO_REF and then runs pnpm install --frozen-lockfile. A stale pin (the SHA from the last release) against a lockfile that already absorbed a newer apps/pro/package.json fails install. This is what hung v0.41.0.
git -C apps/pro status --porcelain # must be empty
git -C apps/pro fetch origin
PRO_SHA="$(git -C apps/pro rev-parse HEAD)"
git -C apps/pro merge-base --is-ancestor "$PRO_SHA" origin/main # HEAD must already be on origin/main
gh variable set KANSOKU_PRO_REF --body "$PRO_SHA"
gh variable get KANSOKU_PRO_REF # must print $PRO_SHA
LAST_TAG=$(git describe --tags --match 'desktop-v*' --abbrev=0)
git log "$LAST_TAG"..HEAD --oneline -- apps/ packages/ patches/ scripts/
test cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.