cli-forge-publish

Publish cli-forge-generated skills via GitHub Release and npm with provenance.

Updated Apr 2, 2026

Search Tags:#automation #npm #github #cli #release #semantic-release

Ready to run

npx skills add https://github.com/ByteLandTechnology/cli-forge --skill cli-forge-publish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cli-forge-publish
Source: https://github.com/ByteLandTechnology/cli-forge/tree/main/cli-forge-publish
Command: npx skills add https://github.com/ByteLandTechnology/cli-forge --skill cli-forge-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end release publishing for generated cli-forge skills, unifying git tags, GitHub Releases, and npm platform/main packages under a single version.

Core Features & Use Cases

Centralizes release orchestration for a generated cli-forge skill, including prerelease bootstrap, per-platform npm packages, and main wrapper package.
Ensures one production release produces synchronized artifacts: tag, GitHub Release with assets, per-platform binaries, and a main npm package.
Use Case: when a generated skill is ready for production, run the release pipeline to publish across all targets with a single command.

Quick Start

Copy this skill into a target repository and run the release harness to publish a new version.

Frequently Asked Questions about cli-forge-publish

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

FAQPage Schema

How do I automate npm and GitHub Release publishing for a CLI tool with a single version?▼

Automating npm and GitHub Release publishing requires a unified pipeline that validates configuration, prepares binaries, and publishes across all targets with one semantic version. This ensures synchronized artifacts including git tags, GitHub Releases, and npm packages.

What is the best way to manage per-platform npm packages and a main wrapper package during a release?▼

Managing per-platform npm packages involves centralizing release orchestration to produce synchronized artifacts. A unified release pipeline handles prerelease bootstrap, per-platform binaries, and the main wrapper package under a single production release.

How do I publish a CLI tool to GitHub and npm with provenance and rollback protections?▼

Publishing with provenance and rollback protections uses an automated pipeline that validates configuration, prepares binaries, and publishes to GitHub and npm. It covers prerelease bootstrap and ensures a single semantic version across all targets.

Can I use semantic-release to synchronize git tags, GitHub Releases, and npm packages for generated CLI skills?▼

Yes, synchronizing git tags, GitHub Releases, and npm packages is achieved through a unified release flow. The pipeline validates configuration, prepares per-platform artifacts, and publishes everything under a single semantic version.

What are the limitations of automating release publishing for generated CLI skills?▼

Limitations depend on the pipeline's scope: it requires copying the skill into a target repository and running the release harness. It focuses on unifying GitHub Releases and npm publication, relying on proper configuration validation and rollback mechanisms.