Ship a change end to end without breaking production. This workflow chains three new plugins to make the risky database change safe, pre-flight the deploy manifests, prepare a clean commit and PR with the right version bump, and triage CI the moment it goes red.
Before the schema change ships, check it for table-locking and blocking operations. SQL Safety Net rewrites unsafe migrations into zero-downtime expand-contract steps and emits a paired rollback - no database connection required.
Validate your Kubernetes manifests before they hit the cluster. The k8s-preflight check catches the silent failures - string-vs-int ports, missing resource limits, absent probes, and no securityContext - and returns corrected YAML.
Turn your diff into a clean Conventional Commit, a recommended semver bump, and a complete PR description. Release Conductor dispatches the semver-advisor to reason about behavioral breaking changes, then drafts everything for you to approve.
If the pipeline fails, don't spelunk through logs. The ci-failure-triager classifies the failure against a taxonomy of GitHub Actions failure modes - permissions, secrets, matrix, cache, triggers - and proposes the exact YAML fix.
Run /migration-safety before anything else. Catching a table-locking ALTER before it reaches staging is the difference between a deploy and an incident.
Let /ship recommend the version bump. The semver-advisor reasons about behavioral breaking changes, not just syntax - it catches the ones humans get wrong about 40% of the time.
Keep the CI & Incident Medic hook enabled. When a build command fails, it offers /gha-triage automatically so you go from red to root cause without digging through logs.