Опишете задачата
Към всички skills

publish-cli

cline · Документация

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.

Оригинален текст · няма потвърден превод на български
Платформи: ClaudeНиво: НапредналоВ индекса: 11.06.2026 г.Обновен в GitHub: 11.06.2026 г.

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md
GitHub хранилище
Звезди на репото
63 049
Лиценз
Не е посочен. Проверете в репозитория.
Последна проверка на записа
Няма посочена дата

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add cline/cline

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.md

Началото на файла на автора, без превод.

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.

Release contract

  • SDK prerequisite: the CLI depends on the SDK via workspace:* (@cline/core, @cline/shared, and friends). If the SDK changed since its last release, release the SDK first and wait for it to finish publishing before releasing the CLI. See "Step 0: Release the SDK first if it changed" below.
  • Version source: apps/cli/package.json.
  • Main release tag: cli-vX.Y.Z, where X.Y.Z matches apps/cli/package.json.
  • Nightly release version: X.Y.Z-nightly.TIMESTAMP.
  • Release prep includes approved release notes, a version bump, and an apps/cli/CHANGELOG.md update.
  • Publish paths:
    • GitHub workflow: .github/workflows/cli-publish.yml.
    • Local publish helper: bun release cli.
  • npm dist-tags and git tags are separate. --tag latest and --tag nightly are npm registry channels. cli-vX.Y.Z is a git tag for source history and GitHub releases.
  • The GitHub main release workflow runs from main, requires an existing cli-vX.Y.Z tag, checks out that tag, and publishes from it.
  • The GitHub nightly workflow publishes to npm with the nightly dist-tag and does not create a tag.
  • The local release helper requires a clean checkout and cli-vX.Y.Z to point at HEAD locally and on origin before publishing.
  • Local GitHub release creation requires gh to be authenticated with release permissions for the repo.
  • Always

Целият SKILL.md в GitHub