Checks whether a release can be undone before it ships – that the previous version is still redeployable (immutable image tags or a platform with native rollback), that the schema after this release's migrations still runs the previous code (read from the migrations gate).
Checks whether a release can be undone before it ships - that the previous version is still redeployable (immutable image tags or a platform with native rollback), that the schema after this release's migrations still runs the previous code (read from the migrations gate), that backups have point-in-time recovery and a recent restore test, that a rollback runbook exists with real commands and a verification step, and that the rollback was rehearsed; drafts the runbook when missing. Use when someone asks "can we roll this back if it breaks", "what's our rollback plan", "write a rollback runbook", "is this deploy reversible", or as the fourth step of a production readiness review. Do NOT use to decide between rolling back and rolling forward during an incident (use rollback-or-roll-forward, then follow the runbook this produces), to plan a staged rollout (use progressive-rollout), or to design a blue-green or canary platform from scratch.This is the skill's description: the text your AI reads to decide when the skill applies.
This is the skill's header. The step-by-step instructions are paid content and aren't shown here.
rollback-path/SKILL.md
---
name: rollback-path
description: Checks whether a release can be undone before it ships - that the previous version is still redeployable (immutable image tags or a platform with native rollback), that the schema after this release's migrations still runs the previous code (read from the migrations gate), that backups have point-in-time recovery and a recent restore test, that a rollback runbook exists with real commands and a verification step, and that the rollback was rehearsed; drafts the runbook when missing. Use when someone asks "can we roll this back if it breaks", "what's our rollback plan", "write a rollback runbook", "is this deploy reversible", or as the fourth step of a production readiness review. Do NOT use to decide between rolling back and rolling forward during an incident (use rollback-or-roll-forward, then follow the runbook this produces), to plan a staged rollout (use progressive-rollout), or to design a blue-green or canary platform from scratch.
---
… the full instructions are part of a premium pack and load in your AI once you have access.