rollback

Generates a numbered production rollback runbook with verification checks and stakeholder communication.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill rollback-jnlanahan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rollback
Source: https://github.com/jnlanahan/Product-Agents-and-Skills/tree/main/skills/6-Deploy-Rollback
Command: npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill rollback-jnlanahan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents extended downtime and cascading failures by generating a clear, ordered rollback plan when a production deploy introduces a regression.

Core Features & Use Cases

  • Regression-aware rollback planning: Confirms production impact, identifies what changed (code, DB migration, env vars, infra/DNS), and classifies rollback complexity before action.
  • Safe sequencing and guardrails: Enforces rollback ordering (rollback code before DB in most cases), warns against editing applied migrations, and calls out data-loss/backup requirements.
  • Runbook generation and guided execution: Produces a numbered step-by-step rollback runbook (including verification checks, estimated time, and stakeholder notifications) and can walk through steps when the user is ready.

Use Case Example: After deploying a new release, your app errors start returning 500s; use this Skill to determine whether the incident is tied to code, an additive vs destructive DB migration, or environment configuration, then generate the correct rollback steps for your platform (Render, Railway, Vercel, Fly.io, or other).

Quick Start

Ask the AI: "Create a rollback plan for the broken production deploy and walk me through it step by step."

Frequently Asked Questions about rollback

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

FAQPage Schema
How do I create a rollback plan for a broken production deployment?

A production rollback plan confirms the regression, classifies rollback complexity by identifying code, database migration, or environment variable changes, and generates a numbered runbook with verification checks. It saves the plan to a markdown file for guided execution.

When do I need to roll back database migrations versus code changes?

Database migration rollback depends on whether the migration is additive or destructive. You generally roll back code changes before database migrations, avoid editing applied migrations, and require data backups when destructive migrations are involved.

Does this deployment rollback workflow support platforms like Render, Railway, Vercel, and Fly.io?

Yes, the rollback runbook generation applies platform-specific deployment rollback workflows for Render, Railway, Vercel, Fly.io, and other platforms, tailoring the steps to each provider's deployment mechanics.

What is the correct sequence for rolling back a production incident caused by environment variable changes?

Rolling back environment variable changes requires identifying the modified variables, reverting them to their previous state, and validating that production is truly restored. The runbook enforces safe sequencing and includes stakeholder communication steps.

Can I walk through a rollback runbook step by step during a production incident?

Yes, after generating the rollback runbook with estimated times and verification checks, the Skill can walk through each numbered step with you during the production incident to ensure safe and guided execution.