release

Automate end-to-end software release management with pre-flight checks, changelog updates, version bumps, git tagging, PR creation, and GitHub release publishing.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/mguinada/ai-coding-toolkit --skill release-mguinada
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/mguinada/ai-coding-toolkit/tree/main/skills/release
Command: npx skills add https://github.com/mguinada/ai-coding-toolkit --skill release-mguinada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing software is a multi-step, error-prone process that requires coordinating checks, changelog updates, version bumps, and communications across teams.

Core Features & Use Cases

  • Pre-flight checks to ensure a clean, releasable state
  • Automated changelog generation and version bump guidance
  • Tag creation, PR drafting, and GitHub release publishing
  • Proactive activation: respond to natural-language release intents like “release” or “cut a release”
  • Use Case: align a sprint’s output with a tagged version and documented release notes

Quick Start

Initiate a release workflow on the main branch to perform pre-flight checks, update the changelog, bump the version, publish a tag, and create a GitHub release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate software release management in a CI/CD workflow?

Automated software release management orchestrates pre-flight checks, version bumps, changelog updates, git tagging, and GitHub release publishing directly within CI/CD pipelines. This ensures a clean, releasable state without manual coordination errors.

What is the best way to generate changelogs and bump versions for a new sprint release?

The best way to generate changelogs and bump versions is through end-to-end release orchestration that performs automated pre-flight checks, updates the changelog, increments the version, and aligns sprint output with a tagged release.

Does this release orchestration process work with GitHub for creating tags and publishing releases?

Yes, release orchestration works directly with GitHub to create git tags, draft pull requests, and publish GitHub releases. It coordinates these steps automatically after verifying a clean main branch state.

Can I trigger a package update and release workflow using natural language commands?

You can trigger package update and release workflows using natural language intents like “release” or “cut a release.” The system proactively activates to initiate the full release orchestration process.

What pre-flight checks are needed before cutting a release on the main branch?

Pre-flight checks for cutting a release ensure the main branch is in a clean, releasable state before proceeding. These checks validate readiness prior to executing changelog updates, version bumps, and git tagging.

Why does releasing software require coordinating multiple steps like version bumps and tagging?

Releasing software requires coordinating multiple steps because it is an error-prone process spanning pre-flight checks, changelog updates, version bumps, and team communications. End-to-end release orchestration automates these tasks to prevent human error.