command-release

Automate software releases with version tags and GitHub Actions.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/aroido/vibesmith --skill command-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-release
Source: https://github.com/aroido/vibesmith/tree/main/.codex/skills/command-release
Command: npx skills add https://github.com/aroido/vibesmith --skill command-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex process of releasing software, including generating release notes, tagging code, and deploying to public repositories, reducing manual effort and potential errors.

Core Features & Use Cases

  • Tag-Driven Releases: Initiates releases based on version tags (e.g., v1.2.3).
  • Automated Release Notes: Generates draft release notes using AI, requiring human review.
  • GitHub Actions Integration: Leverages CI/CD workflows for building and deploying.
  • Use Case: A developer needs to release a new version of the application. They trigger the /release v1.0.0 command, which guides them through AI-assisted note generation, code tagging, and automated build monitoring.

Quick Start

Execute the release command for version v0.5.1.

Frequently Asked Questions about command-release

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

FAQPage Schema
How do I automate software releases with GitHub Actions and version tags?

Automate software releases by triggering GitHub Actions workflows with version tags like v1.2.3. This process manages release note generation, code tagging, build monitoring, and public release verification to reduce manual deployment effort.

Can I generate release notes automatically for a new deployment?

Yes, automated release notes are generated using AI. The system produces a draft of release notes that requires human review before finalizing the deployment, ensuring accuracy and context for the new version.

Does command-release support both standard and auto-bump release flows?

Yes, the release automation supports both standard and auto-bump release flows. Both workflows include rollback capabilities, allowing you to revert deployments if the build monitoring or public release verification identifies an issue.

What's the best way to trigger a deployment for a specific application version?

The best way to trigger a deployment is by executing a release command with the target version, such as /release v1.0.0. This initiates AI-assisted note generation, code tagging, and automated build monitoring via CI/CD workflows.

Why do I need human review for AI-generated release notes?

Human review is required for AI-generated release notes to ensure the drafted content accurately reflects the changes. This verification step happens before code tagging and deployment, preventing incorrect information from reaching public repositories.

Are there limitations when using version tags for CI/CD workflows?

A limitation of using version tags for CI/CD workflows is the strict dependency on the tag format, such as v1.2.3. Deviating from the expected tag structure may prevent the release automation from correctly initiating the build and deployment process.