Agent skill · Documentation

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

kansoku-tradegithub.com/kansoku-tradeGitHub ↗
claude-codeNOASSERTION
Install
npx skills add kansoku-trade/kansoku --skill release --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: .claude/skills/release/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 272
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Desktop Release 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. ## Steps ### 1. Preflight (stop with an explanation if any fails) ```bash 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 ``` ### 2. Collect what shipped ```bash LAST_TAG=$(git describe --tags --match 'desktop-v*' --abbrev=0) git log "$LAST_TAG"..HEAD --oneline -- apps/ packages/ patches/ scripts/ ``` If `git describe` finds no tag, this is the first release — use the full history of those paths. If there are no commits touching `apps/`, `packages/`, `patches/`, or `scripts/` since the last tag, stop: nothing to release. Read the actual diffs of significant commits when the one-line messages aren't enough to describe user-visible changes. #

What's inside
Steps it walks through
  1. Steps
  2. 1. Preflight (stop with an explanation if any fails)
  3. 2. Collect what shipped
  4. 3. Decide the version
  5. 4. Write the release notes
  6. 5. Bump the version
  7. 6. Open the PR
  8. 7. Hand off
  9. Guards
Commands it runs
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
git log "$LAST_TAG"..HEAD --oneline -- apps/ packages/ patches/ scripts/
git checkout -b release/desktop-vX.Y.Z
git add apps/desktop/package.json apps/desktop/CHANGELOG.md
git commit -m "release(desktop): vX.Y.Z"
git push -u origin release/desktop-vX.Y.Z
gh pr create --title "release(desktop): vX.Y.Z" --body "<release notes section>"
More from kansoku
All skills →
About this skill
What does the release skill do?

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

How do I install it?

Run `npx skills add kansoku-trade/kansoku --skill release --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From kansoku-trade/kansoku, a repository with 272 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going