skills.rest
Sheldon-92
Sheldon-92COMMUNITY
Explore all skills by this author →
GitHub

release-runbook

Codify a seven-phase, gate-enabled release and sync workflow for the TAD framework.

3|Updated Sep 27, 2025
Search Tags:#versioning#release#governance#sync#runbook#git-workflow#downstream
One-click install
npx skills add https://github.com/Sheldon-92/TAD --skill release-runbook-sheldon-92
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-runbook
Source: https://github.com/Sheldon-92/TAD/tree/main/.agents/skills/release-runbook
Command: npx skills add https://github.com/Sheldon-92/TAD --skill release-runbook-sheldon-92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The runbook provides a structured, gate-based process for releasing and syncing TAD versions across downstream projects, preventing recurring release errors by codifying pre-flight checks, version bumps, changelog updates, and post-flight verification.

Core Features & Use Cases

  • Seven-phase framework: Pre-flight, Version Bump, CHANGELOG, Publish, Sync Script, Execute Sync, and Verify, with mandatory gates at each stage to ensure quality and traceability.
  • Guarded release workflow: ensures you only publish or sync after all checks pass, reducing drift and misconfigurations in downstream projects.
  • Post-release verification: validates targets, updates sync registries, and confirms capability packs installation to maintain alignment across environments.

Quick Start

Read this runbook before starting any release tasks to ensure a clean, gate-driven process.

Frequently Asked Questions about release-runbook

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

FAQPage Schema
What is a structured release and sync workflow for downstream projects?▼

A structured release and sync workflow is a gate-enabled process that governs version bumps, changelog updates, publishing, and per-project synchronization to prevent drift across downstream projects.

How do I prevent version drift when publishing updates to downstream projects?▼

To prevent version drift during publishing, enforce mandatory pre-flight checks, registry validation, and post-flight verification gates across all synchronization targets before completing the release.

What are the required phases for a governed git-workflow release?▼

A governed git-workflow release requires seven phases: Pre-flight, Version Bump, CHANGELOG, Publish, Sync Script, Execute Sync, and Verify, with mandatory quality gates at each stage.

How do I verify a successful version sync across multiple downstream projects?▼

Verify a successful version sync by validating targets, updating sync registries, and confirming capability packs installation to maintain alignment across all downstream environments.

Can I execute a downstream project sync without passing pre-flight checks?▼

No, the guarded release workflow enforces mandatory pre-flight checks and gates at each phase, ensuring you only publish or sync after all version reference and registry validations pass.

Related Skills

Explore More Software Engineering Skills→
chrislyonschrislyons

git.release.prep

Automates release prep with semantic versioning, changelog generation, and GitHub publishing.

Community
Intermediate
wrcopilot-orgwrcopilot-org
2

post-migration-validator

Validate post-migration target disks with boot, partition, and health checks.

Official
Advanced
SPANDigitalSPANDigital
39

release-cel2sql

Automate cel2sql release preparation with version bumps, CHANGELOG updates, and PR creation.

Official
Advanced
ACuberoACubero

ci-cd-pipelines

Automate Python CI/CD pipelines with GitHub Actions for testing, linting, and releases.

Community
Advanced