skills.rest
emmepra
emmepraCOMMUNITY
Explore all skills by this author →
Website𝕏@emmepraGitHub

release-train

Group dev PRs into a main release PR with CI and rollback checks.

1|1|Updated Apr 18, 2026
Search Tags:#rollback#release#release-notes#pr-management#ci-verification#dev-to-main
One-click install
npx skills add https://github.com/emmepra/ora-et-labora --skill release-train
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-train
Source: https://github.com/emmepra/ora-et-labora/tree/main/skills/release-train
Command: npx skills add https://github.com/emmepra/ora-et-labora --skill release-train

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates and streamlines release planning by consolidating accumulated work from dev into a single, stable main release with clear scope and rollback readiness.

Core Features & Use Cases

  • Group related implementation PRs from dev into a cohesive release PR and document the release scope.
  • Verify readiness via CI status, browser verification when frontend work is included, and migration/rollback readiness; generate release notes and operational notes.
  • Communicate the release plan and post-release tasks to maintainers and stakeholders.

Quick Start

Bundle prepared changes from dev into a main release PR and generate a concise release summary.

Frequently Asked Questions about release-train

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

FAQPage Schema
How do I group multiple implementation PRs from dev into a single main release?▼

To group implementation PRs into a main release, this Skill consolidates accumulated work from dev into a structured release PR. It identifies the release scope, verifies CI status, and prepares the PR body with release notes.

What is the best way to verify CI status and readiness before promoting dev to main?▼

Verifying readiness before a dev-to-main release involves checking CI status and confirming migration or rollback preparations. This Skill assesses these readiness criteria and documents operational notes to ensure a stable main release.

How do I generate release notes and rollback documentation for a dev-to-main PR?▼

Generating release notes and rollback documentation for a dev-to-main release PR is handled by this Skill. It prepares a structured PR body that includes the identified release scope, necessary migrations, and operational rollback notes.

Can I coordinate a grouped release PR if frontend work requires browser verification?▼

Yes, you can coordinate a grouped release PR that includes frontend work. The release readiness verification process explicitly accounts for browser verification alongside CI status checks before promoting dev to main.

When do I need a structured release train workflow for accumulated dev branch work?▼

You need a structured release train workflow when multiple implementation PRs have accumulated on the dev branch. It streamlines release planning by bundling these changes into a cohesive, stable main release with clear scope and rollback readiness.

Related Skills

Explore More Software Engineering Skills→
me2reshme2resh
489

release-sync

Create a main-to-dev PR with `-X ours` after a squash-merge release.

Community
Advanced
chf3198chf3198

role-admin-execution

Executes governance checks and automated workflows for GitLab CI/CD across multiple stages.

Community
Advanced
h-4vokh-4vok

repo-validate

Run lint, typecheck, test, smoke, and build checks across a repository and emit a pass/fail report.

Community
Intermediate
sgcarstrendssgcarstrends
21

release-management

Automate software release workflows with semantic-release and conventional commits.

Official
Advanced