cut-release

Create a Gait release tag from main and monitor CI validation with bounded hotfix loops.

12|5|Updated Feb 5, 2026

Search Tags:#git #workflow #validation #release #hotfix #tagging #ci

Ready to run

npx skills add https://github.com/Clyra-AI/gait --skill cut-release-clyra-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cut-release
Source: https://github.com/Clyra-AI/gait/tree/main/.agents/skills/cut-release
Command: npx skills add https://github.com/Clyra-AI/gait --skill cut-release-clyra-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cut-release automates tagging a new Gait release directly from main, and coordinates monitoring of release validation and post-release checks along with bounded hotfix loops when failures are actionable.

Core Features & Use Cases

Tag from main to publish releases in a verified workflow.
Monitor release/post-release CI runs and automatically re-run hotfix loops up to two iterations when needed.
Enforce safeguards: no destructive changes, ensure fast-forward syncing of main before tagging, and cap the hotfix loop count.

Quick Start

Run gait cut-release with a version argument to create the tag and trigger the monitored release workflow.

Frequently Asked Questions about cut-release

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

FAQPage Schema

How do I automate git release tagging from main and trigger CI validation?▼

Automating git release tagging from main creates a verified release tag and triggers CI validation. This workflow ensures safe tag creation directly from the main branch while coordinating post-release checks.

What is a bounded hotfix loop in a release workflow?▼

A bounded hotfix loop in a release workflow automatically re-runs hotfix cycles when validation failures are actionable, capping iterations at a maximum of two loops to prevent infinite cycling.

How do I ensure non-destructive operations when cutting a release tag?▼

Ensuring non-destructive operations when cutting a release tag requires enforcing fast-forward syncing of main before tagging. This safeguard prevents destructive changes during the release workflow.

Can I monitor post-release CI checks and automatically re-run failed hotfixes?▼

You can monitor post-release CI checks and automatically re-run failed hotfixes up to two iterations. This bounded hotfix loop applies only when failures are actionable within the release workflow.

What are the limitations of automated release tag creation and hotfix looping?▼

Limitations of automated release tag creation include capping the hotfix loop count at two iterations and requiring fast-forward syncing of main. The workflow does not perform destructive changes during tagging.