publish-cli

Automate Cline CLI releases with versioning, changelogs, and npm distribution.

65.9k|7.1k|Updated Jul 6, 2024
One-click install
npx skills add https://github.com/cline/cline --skill publish-cli-cline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-cli
Source: https://github.com/cline/cline/tree/main/.cline/skills/publish-cli
Command: npx skills add https://github.com/cline/cline --skill publish-cli-cline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the complex, multi-step process of releasing the Cline CLI, ensuring that versioning, changelog updates, SDK synchronization, and publishing workflows are handled consistently and safely.

Core Features & Use Cases

  • Release Orchestration: Manages the dependency chain between the SDK and CLI to ensure hub compatibility and version alignment.
  • Automated Workflow Integration: Triggers GitHub Actions for standardized publishing or guides local releases with proper tagging and authentication checks.
  • Use Case: When a new feature is ready for the CLI, use this skill to verify SDK dependencies, draft release notes from commit history, bump versions, and execute the release pipeline without manual errors.

Quick Start

Use the publish-cli skill to prepare and publish the next version of the CLI by following the guided release workflow.

Frequently Asked Questions about publish-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate npm publishing and versioning for a CLI in a monorepo?

Automated CLI release workflows coordinate cross-package dependencies within a monorepo to ensure SDK and CLI version synchronization. They execute versioning, changelog generation, and npm distribution via GitHub Actions or local CLI helpers while enforcing strict tagging and testing requirements.

How does automated changelog generation work during a CLI release?

Automated changelog generation works by drafting release notes directly from your commit history. This ensures that version updates and changelog entries are handled consistently and safely without manual errors during the CLI release pipeline.

Can I use GitHub Actions for CLI publishing instead of local CLI helpers?

Yes, GitHub Actions can trigger standardized publishing workflows for CLI releases. Alternatively, local CLI helpers can guide the release process, with both methods enforcing strict tagging and testing requirements to ensure safe npm distribution.

Do I need to manually update SDK dependencies before publishing the CLI?

No, you do not need to manually update SDK dependencies. The release orchestration manages the dependency chain between the SDK and CLI automatically to ensure hub compatibility and version alignment before executing the release pipeline.

What are the limitations of automating CLI releases with strict tagging requirements?

The limitation of automating CLI releases with strict tagging requirements is that both GitHub Actions and local CLI helper workflows enforce strict tagging and testing checks, preventing releases from proceeding if version synchronization or testing requirements are not met.