release-cli

Automate opentraces CLI releases with version updates, tests, Git operations, and GitHub releases.

92|6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/JayFarei/opentraces --skill release-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-cli
Source: https://github.com/JayFarei/opentraces/tree/main/.claude/skills/release-cli
Command: npx skills add https://github.com/JayFarei/opentraces --skill release-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the release process of the opentraces CLI, automating version updates, testing, commit/tagging, and GitHub release creation, saving time and reducing errors.

Core Features & Use Cases

  • Version Bumping: Automatically increments version numbers for patch, minor, or major releases.
  • File Updates: Ensures all relevant files are updated with the new version.
  • Build Verification: Runs tests and verifies the build to ensure stability before release.
  • Git Operations: Handles commits, tags, and pushes to the repository.
  • GitHub Release: Creates a GitHub release that triggers PyPI publish and Homebrew formula update.
  • Monitoring: Monitors the publish workflow for successful completion.

Quick Start

Run the skill with the command "release" to automate the release process for opentraces CLI.

Frequently Asked Questions about release-cli

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

FAQPage Schema
How do I automate CLI release processes including version updates and GitHub releases?

Automating CLI release processes involves managing version bumping, file updates, build verification, Git operations, and GitHub release creation. This Skill coordinates PyPI and Homebrew publication while monitoring the publish workflow for successful completion.

What is the best way to automate version bumping and Git tagging for a CLI release?

The best way to automate version bumping and Git tagging is by incrementing patch, minor, or major release numbers, updating relevant files, and handling Git commits and tags before pushing to the repository for release.

Do I need a local build environment and Git repository to automate CLI releases?

Yes, automating CLI releases requires a local build environment and a Git repository. These prerequisites are necessary to run build verification tests and execute the Git operations needed for creating tags and pushing commits.

Can I trigger PyPI publish and Homebrew formula updates with GitHub release automation?

Yes, GitHub release automation can trigger PyPI publish and Homebrew formula updates. Creating a GitHub release through this Skill initiates these downstream publications and monitors the workflow for successful completion.

How does build verification work before creating a GitHub release for a CLI?

Build verification before a GitHub release works by running tests and verifying the build to ensure stability. This process occurs automatically after version updates and before Git operations and release creation are executed.

What are the limitations of automating release processes for the opentraces CLI?

Limitations of automating release processes include its specific design for the opentraces CLI, dependency on a local build environment, and the requirement of an existing Git repository to execute version control and publication tasks.