// This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and optionally publish to npm. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".
Drive the claude-code-kanban browser dashboard from this Claude session. Use this skill when the user mentions "kanban" together with "session" — e.g. "open this session in kanban", "show kanban", "focus current session in kanban", "pin/unpin a session in kanban", "preview this file in kanban", or asks to peek/view a kanban session.
Run code quality checks on the claude-code-kanban project. Use this skill whenever the user wants to check code formatting, linting, or overall code quality for the public/app.js and public/style.css files. Trigger on phrases like "check quality", "lint", "format check", "style check", "quality gates", or any mention of code quality/standards.
| name | release |
| description | This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and optionally publish to npm. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate". |
| argument-hint | [version | rc] |
| allowed-tools | Read, Bash(git *), Bash(gh *), Bash(bun *) |
Bump version, tag, push, create a GitHub release with auto-generated notes, and present npm publish command. Supports both stable releases and release candidates (RC).
$ARGUMENTS — target version (e.g. 1.15.0), rc for release candidate, or empty for auto-detection.Determine release type from $ARGUMENTS and current branch:
$ARGUMENTS contains rc, or current branch is not main/master → RC release$ARGUMENTS is a version like 1.15.0-rc.1 → RC release with that exact versionRun git status --short. If there are uncommitted changes, warn the user and stop.
git branch --show-current
main or master. If not, warn and ask to confirm or switch to RC.Read current version from package.json. If $ARGUMENTS is an exact version, use it directly.
For stable releases:
Analyze commits since the last stable tag (exclude RC tags) to suggest a bump type:
Present the suggested bump type and resulting version to the user using AskUserQuestion with options: patch, minor, major (put the recommended one first with "(Recommended)" suffix).
For RC releases:
1.19.0-rc.1), auto-increment: 1.19.0-rc.21.18.0), determine the next minor/patch version and append -rc.1AskUserQuestion with options showing the auto-incremented version and a "next minor RC" / "next patch RC" alternative.Update version field in package.json to the target version.
git add package.json
git commit -m "🔖 chore: Bump version to <version>"
git push origin <current-branch>
Note: push to the current branch, not hardcoded main.
git tag v<version>
git push origin v<version>
Collect commits since previous tag:
git log --oneline <prev-tag>..HEAD
Group by type:
Write concise user-facing notes (not raw commit messages). Include a Full Changelog compare link using the repository URL from package.json.
Stable release:
gh release create v<version> --title "v<version>" --notes "<notes>"
RC release:
gh release create v<version> --title "v<version>" --notes "<notes>" --prerelease
Show the release URL. Then present the user with the manual publish command:
Stable release:
npm publish
RC release:
npm publish --tag rc
Explain: --tag rc prevents the RC from becoming the latest dist-tag. Users install via npm install <pkg>@rc or npx <pkg>@rc.
Do not run npm publish automatically — let the user decide.