Publish CLI
Use when preparing, tagging, and publishing an apps/cli npm release.
Install
npx skills add cline/cline --skill publish-cli -g -a claude-code -y- Repository
- cline/cline71.2k
- Category
- Git and review
- Updated
- 4d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use when preparing, tagging, and publishing an apps/cli npm release. Guides changelog drafting, apps/cli/package.json version bumps, cli-vX.Y.Z tags, local npm publishing, and the publish-cli GitHub workflow.
CLI Release
Use this skill when the user asks to release the CLI, publish cline, bump the CLI version, draft release notes, create a cli-vX.Y.Z tag, or trigger the CLI publish workflow.
The CLI is npm-only. Do not add alternate distribution channels. Windows binaries are Authenticode-signed automatically by the publish workflow via Azure Trusted Signing (see the .github/actions/sign-windows-cli composite action and "Windows code signing" in apps/cli/DISTRIBUTION.md); if the signing secrets are not configured the workflow warns and publishes unsigned binaries. Local publishes (bun release cli) do not sign, prefer the GitHub Actions publish path for releases users run on Windows.
Working directory: run every command below from the repository root. Paths and scripts (e.g.
apps/cli/package.json,sdk/packages/,bun release cli,bun run version) are written relative to the repo root.
The skill should guide the user through one release preparation flow, then offer the publish path options. The two normal publish paths are GitHub Actions and local publishing from an authenticated machine.
