skills.rest
productiveio
productiveioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

cli-toolbox_publish

Manage cli-toolbox monorepo releases with version bumping and git tagging.

Updated Mar 7, 2026
Search Tags:#versioning#deployment#cli#github actions#release#publish
One-click install
npx skills add https://github.com/productiveio/cli-toolbox --skill cli-toolbox-publish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cli-toolbox_publish
Source: https://github.com/productiveio/cli-toolbox/tree/main/.claude/skills/cli-toolbox_publish
Command: npx skills add https://github.com/productiveio/cli-toolbox --skill cli-toolbox-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of releasing new versions of the cli-toolbox binaries, automating version bumping, tagging, and deployment.

Core Features & Use Cases

  • Automated Version Management: Handles bumping versions across multiple crates.
  • Git Tagging & Pushing: Creates and pushes git tags, ensuring proper CI triggers.
  • Local Installation: Optionally installs the newly released binaries locally.
  • Use Case: When a new feature is merged into tb-prod, use this Skill to automatically bump its version, tag the release, push the tag, and install the updated binary on your system.

Quick Start

Publish the new version of the tb-prod tool to 0.3.0 and install it locally.

Frequently Asked Questions about cli-toolbox_publish

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

FAQPage Schema
How do I automate CLI binary version bumping and release in a monorepo?▼

Automating CLI binary version bumping in a monorepo involves bumping versions across multiple crates, creating git tags, and pushing them sequentially to trigger GitHub Actions deployment workflows.

How do I publish a specific binary from a workspace without releasing all tools?▼

To publish a specific binary from a workspace without releasing all tools, you can configure the release process to target individual tools within the workspace rather than building and tagging the entire suite.

Why do my GitHub Actions release workflows fail to trigger when pushing multiple git tags?▼

Pushing multiple git tags simultaneously often causes GitHub Actions release workflows to fail to trigger; pushing tags sequentially ensures proper CI triggering and reliable deployment execution.

Can I install a newly released CLI binary locally as part of the deployment process?▼

Yes, you can install a newly released CLI binary locally as part of the deployment process by enabling conditional local installation of specified binaries after version bumping and git tagging complete.

What is the best way to manage end-to-end CLI tool releases across multiple crates?▼

The best way to manage end-to-end CLI tool releases across multiple crates is using an automated process that handles version bumping, git tagging, and conditional local installation sequentially.

Related Skills

Explore More Software Engineering Skills→
edictum-aiedictum-ai
29

release

Automate semantic version bumping, tagging, pushing, and GitHub Release creation.

Official
Intermediate
dodygdodyg

dotnet-github-releases

Create and manage GitHub Releases for .NET projects with tag-based workflows.

Community
Intermediate
CodingThrustCodingThrust
35

release

Automate Rust crate releases with SemVer versioning and crates.io publishing.

Official
Intermediate
christophevgchristophevg

release

Bump C3 plugin versions, update changelogs, and push annotated git tags.

Community
Intermediate