release

Orchestrate beta-to-main releases with branch sync, PR creation, CI gates, and documentation.

4|3|Updated Feb 7, 2026

Search Tags:#documentation #release #pr #epic #ci #beta #main

Ready to run

npx skills add https://github.com/steilerDev/cornerstone --skill release-steilerdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/steilerDev/cornerstone/tree/main/.claude/skills/release
Command: npx skills add https://github.com/steilerDev/cornerstone --skill release-steilerdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promotes beta to main by coordinating branch sync, PR creation, CI gates, and comprehensive documentation, enabling a safe and auditable release process. It can operate standalone or as part of an epic-close flow to enrich the promotion with epic context.

Core Features & Use Cases

Branch synchronization between main and beta with a promotion PR from beta to main
CI gate validation and merge readiness checks prior to merging
Documentation updates and epic-close integration to keep release notes current
Flexible execution: standalone or delegated from /epic-close for epic-bound releases

Quick Start

Promote the beta branch to main using the release skill, optionally supplying an epic number to enrich the promotion PR.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate a beta-to-main branch release with CI gates?▼

To automate a beta-to-main release, you orchestrate branch synchronization, promotion PR creation, and CI gate validation. This enforces merge readiness checks and maintains an auditable release process before integrating beta changes into main.

What is the safest way to promote a beta branch to main?▼

The safest way to promote a beta branch is by using a guided, step-by-step workflow with task tracking and merge validation. This coordinates branch synchronization and CI gates to ensure only validated changes are merged into main.

How do I include epic context in a beta-to-main promotion PR?▼

To include epic context in a beta-to-main promotion PR, you run the release process as part of an epic-close flow. This enriches the promotion with epic-specific details and updates documentation to keep release notes current.

Do I need a specific CI tool to validate merge readiness for releases?▼

No specific CI tool is required. The release process validates CI gates and performs merge readiness checks generically, ensuring all required validations pass before allowing the promotion PR to merge into main.

Can I run a beta-to-main release standalone without an epic?▼

Yes, you can run a beta-to-main release standalone. It operates independently to coordinate branch synchronization, PR creation, and documentation updates, or it can be delegated from an epic-close flow for epic-bound releases.

How do I keep documentation updated when syncing main and beta branches?▼

To keep documentation updated when syncing main and beta branches, the release workflow integrates documentation updates into the promotion process. This ensures release notes remain current and comprehensive during the beta-to-main merge.