skills.rest
ronniegeraghty
ronniegeraghtyCOMMUNITY
Explore all skills by this author →
GitHub

release-process

Enforce a release checklist for version bumps, tagging, GitHub releases, and rollback procedures.

3|5|Updated Mar 19, 2026
Search Tags:#versioning#rollback#release#semver#ci-cd#process
One-click install
npx skills add https://github.com/ronniegeraghty/hyoka --skill release-process-ronniegeraghty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/ronniegeraghty/hyoka/tree/main/.squad/templates/skills/release-process
Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill release-process-ronniegeraghty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a definitive, zero‑tolerance release runbook that enforces a strict, auditable checklist to prevent Squad release disasters.

Core Features & Use Cases

  • Version validation and multi-step checks ensure consistent semver across all packages and prevent invalid releases.
  • Branch, tag, and release workflow enforcement guides creating and publishing a GitHub Release with proper tagging, and disables risky autopatch/bump steps during releases.
  • Rollback and remediation guidance covers steps to revert or deprecate broken releases and restore production stability.
  • Use Case: Before shipping Squad, run the checklist to verify versioning, release notes, and access controls to minimize deployment errors.

Quick Start

Follow this checklist verbatim before issuing a Squad release.

Frequently Asked Questions about release-process

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

FAQPage Schema
How do I enforce a strict release checklist to prevent deployment disasters?▼

A defensive release process enforces a rigorous, zero-tolerance checklist for version bumps, tagging, and GitHub releases to prevent deployment disasters. It validates semver, governs tokens, and ensures auditable records for safe, repeatable releases.

How do I validate semver and manage GitHub release tags correctly?▼

To validate semver and manage GitHub release tags, the release process enforces multi-step checks for consistent versioning across packages. It guides the creation and publishing of GitHub Releases with proper tagging while disabling risky autopatch steps.

What is the best way to rollback a broken release and restore production stability?▼

The best way to rollback a broken release is to follow dedicated rollback and remediation guidance within a release process. This provides specific steps to revert or deprecate broken releases and restore production stability safely.

Does a CI-CD release process need to verify access controls before shipping?▼

Yes, a CI-CD release process needs to verify access controls before shipping. It applies token governance and checks release notes and access controls to minimize deployment errors before issuing a release.

When should I disable autopatch or bump steps during a release workflow?▼

You should disable autopatch or bump steps during a release workflow when enforcing strict branch, tag, and release workflows. This prevents risky automated version changes and ensures manual validation of the release process.

Related Skills

Explore More Software Engineering Skills→
coff33ninjacoff33ninja

release-changelog

Automates SemVer-Compliant release workflows including bumping versions, updating changelogs, and triggering CI/CD pipelines for diverse programming languages and systems.

Community
Advanced
elcoospelcoosp

rm

Manage production release processes with pre-release checklists and rollback procedures.

Community
Advanced
sudhakrmssudhakrms
1

release-process

Automate and govern software releases with validation and rollback procedures.

Community
Advanced
bradygasterbradygaster
3

ci-validation-gates

Validate semver, verify NPM token types, and retry registry operations.

Community
Advanced