Orchestrate beta-to-main releases with branch sync, PR creation, CI gates, and documentation.
npx skills add https://github.com/steilerDev/cornerstone --skill release-steilerdev
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
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.
Promote the beta branch to main using the release skill, optionally supplying an epic number to enrich the promotion PR.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
Jason-Clark-FGValidate UI changes on feature branches with Playwright end-to-end tests.
fcastrilloCloses a project epic by finalizing gradebook entries, aggregating statistics, and reopening the next epic.
steilerDevAutomate epic closure by coordinating refinement, validation, and promotion to main.
auldsyababuaAnalyze Git branch merge conflicts with an 8-step workflow.
