publish-ui

Automate versioning, validation, and npm publication for the @cline/ui package.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the complex, multi-step process of versioning, validating, and publishing the @cline/ui package, ensuring consistency and preventing manual errors during release cycles.

Core Features & Use Cases

  • Release Validation: Automates type checking, unit testing, and package integrity verification before publication.
  • Channel Management: Safely handles both production (latest) and preview (next) npm release channels.
  • Trusted Publishing: Configures and manages GitHub-to-npm trusted publishing workflows to eliminate the need for long-lived access tokens.

Quick Start

Use the publish-ui skill to prepare and publish a new patch version of the UI package to the latest npm channel.

Frequently Asked Questions about publish-ui

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

FAQPage Schema
How do I automate npm package publishing with GitHub Actions and Bun?

Automating npm package publishing requires configuring GitHub Actions workflows to handle versioning, validation, and deployment. This Skill orchestrates the publication lifecycle for the @cline/ui package using Bun for package management and GitHub Actions for automated trusted deployments.

What is GitHub-to-npm trusted publishing and how does it eliminate access tokens?

GitHub-to-npm trusted publishing configures CI/CD workflows to authenticate directly with npm via OIDC, eliminating the need for long-lived access tokens. This approach establishes a trusted relationship between your GitHub repository and the npm registry to secure releases.

How do I manage both latest and preview npm release channels for a UI package?

Managing npm release channels involves safely routing validated builds to production (latest) or preview (next) distributions. This Skill handles channel management by automating the routing logic during the package publication lifecycle for the @cline/ui package.

Do I need Bun to use this npm publishing automation workflow?

Yes, Bun is required as the package manager to execute this npm publishing workflow. The automation relies on Bun to manage dependencies and run the validation, versioning, and publication scripts defined in the GitHub Actions CI/CD pipeline.

What validation steps are required before publishing an npm package in CI/CD?

Validating an npm package before publication requires automating type checking, unit testing, and package integrity verification. This Skill executes these validation checks within the CI/CD pipeline to ensure consistency and prevent manual errors during the release cycle.

How does semver compliance work when automating package versioning in CI/CD?

Semver compliance during automated package versioning ensures that release versions follow semantic versioning rules before deployment. This Skill automates versioning and validation to enforce semver compliance across the @cline/ui package publication lifecycle.