release

Automate the end-to-end software release lifecycle with git operations and CI/CD monitoring.

94|7|Updated May 9, 2026
One-click install
npx skills add https://github.com/Sma1lboy/kobe --skill release-sma1lboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Sma1lboy/kobe/tree/main/.claude/skills/release
Command: npx skills add https://github.com/Sma1lboy/kobe --skill release-sma1lboy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex, multi-step process of cutting a software release, ensuring consistency while preventing common errors like accidental minor version bumps or releasing from the wrong branch.

Core Features & Use Cases

  • Automated Release Pipeline: Orchestrates the entire flow from changeset detection and gate validation to tagging and npm publishing.
  • Safety Guardrails: Enforces strict branch verification, prevents force-pushes, and provides human-in-the-loop gates for critical versioning decisions.
  • CI/CD Integration: Monitors GitHub Actions workflows and provides precise diagnostic reports for failures, ensuring the release is fully verified before completion.

Quick Start

Ask the agent to cut a new release for the kobe project and it will handle the versioning, testing, and publishing process for you.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate git operations and npm publishing for a new software release?

Automated release pipelines coordinate git operations, changeset versioning, and CI/CD monitoring to ensure version integrity and deployment success. They enforce strict branch verification and provide human-in-the-loop gates for critical versioning decisions.

How do I prevent accidental minor version bumps or releases from the wrong git branch?

To prevent accidental version bumps, the system enforces strict branch verification, blocks force-pushes, and provides human-in-the-loop gates for critical versioning decisions. This ensures versioning consistency and prevents releasing from the wrong branch.

Do I need GitHub CLI and Bun installed to automate my CI/CD release pipeline?

Yes, automating the end-to-end release pipeline requires integration with GitHub CLI, Bun, and local test suites. These dependencies are necessary to validate versions, monitor GitHub Actions workflows, and publish releases autonomously.

How can I monitor GitHub Actions workflows and diagnose CI/CD failures during a release?

You can monitor GitHub Actions workflows during a release to receive precise diagnostic reports for failures. This CI/CD integration ensures the release is fully verified before completion, preventing faulty deployments.

What are the limitations of autonomous end-to-end release automation?

Autonomous release automation operates strictly within git-based development workflows and requires specific dependencies like Bun and GitHub CLI. It cannot bypass human-in-the-loop gates for critical versioning decisions, ensuring safety over full autonomy.