skills.rest
rp4ri
rp4riCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release-train

Enforce release guardrails for tag-driven multi-platform CI/CD workflows.

Updated Jun 4, 2026
Search Tags:#ci/cd#github actions#release automation#schema migration#release verification#multi-platform releases#tag-driven deployments
One-click install
npx skills add https://github.com/rp4ri/orchestration-studio --skill release-train-rp4ri
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-train
Source: https://github.com/rp4ri/orchestration-studio/tree/main/skills/release-train
Command: npx skills add https://github.com/rp4ri/orchestration-studio --skill release-train-rp4ri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the high risk of costly production incidents during multi-platform releases, including stale tag deployments that ship unfixed code, silent schema migration failures that break features, and deployments to the wrong execution tier that leave bugs unfixed for end users, all of which require hours of debugging and rollback effort.

Core Features & Use Cases

  • Per-platform independent release cadences: Configure separate tag namespaces for macOS, Windows, Android, and server deployments so each platform builds only when its tag is pushed, eliminating unnecessary CI costs and avoiding forced backend restarts for UI-only changes.
  • Pre-release guardrails: Enforce execution tier mapping and schema-coupled release validation to ensure fixes are deployed to the correct runtime tier and database migrations run before dependent code is shipped.
  • Safe failure recovery: Provide step-by-step procedures for safely re-triggering failed builds without version bumps (if no artifacts were published) and background run watchers with built-in post-release verification to catch issues immediately after deployment.
  • Use Case: A team shipping a cross-platform desktop app with a separate backend server can use this Skill to ensure a UI-only fix only triggers a desktop build, a database schema change runs its migration before the app is deployed, and a failed Windows build is safely re-triggered without publishing a new version if no artifacts were released.

Quick Start

Use the release-train skill to safely cut a new tagged multi-platform release, run pre-flight checks for execution tier and schema migration coverage, and configure background watchers for post-release verification.

Frequently Asked Questions about release-train

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

FAQPage Schema
How do I prevent stale tag deployments in multi-platform CI/CD workflows?▼

Prevent stale tag deployments in multi-platform CI/CD workflows by enforcing pre-release guardrails that map execution tiers and validate schema migrations before dependent code is shipped. This stops unfixed code from reaching production and eliminates manual rollback effort.

How do I set up independent release cadences for cross-platform desktop and mobile applications?▼

Set up independent release cadences for cross-platform desktop and mobile applications by configuring separate tag namespaces for each platform. This ensures each platform builds only when its specific tag is pushed, eliminating unnecessary CI costs and preventing forced backend restarts for UI-only changes.

Can I safely re-trigger failed CI/CD builds without publishing a new version?▼

You can safely re-trigger failed CI/CD builds without publishing a new version by following specific recovery procedures. If no artifacts were published during the failed run, you can re-trigger the build without applying a version bump, avoiding unnecessary release cycles.

What is schema-coupled release validation for tag-driven deployments?▼

Schema-coupled release validation for tag-driven deployments is a pre-release guardrail ensuring database migrations run before dependent application code is shipped. This prevents silent schema migration failures that break features and cause costly production incidents.

How do I monitor post-release artifact and service health after automated deployments?▼

Monitor post-release artifact and service health after automated deployments by configuring background run watchers with built-in post-release verification. These watchers catch issues immediately after deployment, preventing silent failures from affecting end users.

Does tag-driven release automation work for teams with separate server and desktop release cycles?▼

Tag-driven release automation works effectively for teams with separate server and desktop release cycles by applying per-platform independent release cadences. This ensures fixes deploy to the correct runtime tier while avoiding unnecessary builds for unrelated platforms.

Related Skills

Explore More Software Engineering Skills→
j0rugej0ruge
8

cicd

Diagnose and fix CI/CD pipelines across GitHub Actions, Docker, and GHCR.

Community
Advanced
pfangueiropfangueiro
6

deployment-runbook

Standardize production deployment runbooks with health checks and rollback strategies.

Community
Intermediate
Pravin-surawasePravin-surawase
5

quality-gate

Enforce mandatory quality checks for production code changes.

Community
Advanced
Kling0012Kling0012
1

github-workflow-automation

Automate GitHub workflow orchestration and CI/CD management across repositories.

Community
Advanced