cut-release

Automate Gait release tag creation from main with validation and hotfix loops.

12|5|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/davidahmann/gait --skill cut-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cut-release
Source: https://github.com/davidahmann/gait/tree/main/.agents/skills/cut-release
Command: npx skills add https://github.com/davidahmann/gait --skill cut-release

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the complex and error-prone process of cutting new software releases, ensuring code quality and stability through rigorous validation and controlled hotfix loops.

Core Features & Use Cases

  • Automated Release Tagging: Creates and pushes version tags directly from the main branch.
  • Monitored Release Validation: Tracks GitHub Actions workflows for release and post-release UAT, stopping on failures.
  • Bounded Hotfix Loops: Manages up to two hotfix cycles for actionable release failures, including PR creation, CI monitoring, and merging.
  • Use Case: A developer needs to release version v1.2.0 of the Gait project. This Skill will tag main, monitor the release CI, run UAT, and if any step fails, it will create a hotfix branch, fix the issue, open a PR, get it merged, and then create a new tag for v1.2.1 if necessary, repeating this process up to two times.

Quick Start

Use the cut-release skill to cut a new release tag for version v1.2.0 from the main branch.

Frequently Asked Questions about cut-release

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

FAQPage Schema
How do I automate release management and cut a new tag from the main branch?

Automated release management cuts a version tag directly from the main branch, synchronizes with origin/main, and performs extensive pre-tag validation to ensure code integrity before pushing.

Does continuous integration deployment validation support hotfix PR loops?

Continuous integration deployment validation supports up to two bounded hotfix PR loops, automatically creating hotfix branches, monitoring CI workflows, and merging fixes when release failures are actionable.

What's the best way to handle GitHub Actions workflow monitoring during a deployment?

Handling GitHub Actions workflow monitoring during deployment involves tracking release and post-release UAT workflows, stopping execution immediately upon detecting validation failures.

Can I use local UAT to validate a release tag before announcing it?

You can use local UAT to validate a release tag before announcing it, as the process monitors GitHub workflows and runs local UAT to verify stability before completing the release cycle.

How does git tagging normalization work for input versions like v1.2.0?

Git tagging normalization handles input version formatting directly, ensuring version strings are standardized before creating and pushing the new release tag from the main branch.