rollback

Analyze deployments and migrations to generate prioritized rollback safety checklists.

5|2|Updated Dec 11, 2025

Search Tags:#checklist #deployment #rollback #migrations #safety #feature-flags #incident-response

Ready to run

npx skills add https://github.com/thoreinstein/opencode-config --skill rollback-thoreinstein

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rollback
Source: https://github.com/thoreinstein/opencode-config/tree/main/skill/rollback
Command: npx skills add https://github.com/thoreinstein/opencode-config --skill rollback-thoreinstein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze deployment or change for rollback safety and generate a prioritized checklist to minimize downtime and data risk. Documents findings to Obsidian for traceability and post-incident learning.

Core Features & Use Cases

Rollback risk assessment: evaluates code changes, migrations, and config changes for reversibility and safety.
Parallel investigation: runs codebase exploration, migration analysis, and external research tracks to surface blockers.
Safety categorization: labels changes as Safe to Rollback, Requires Caution, or Potentially Dangerous with actionable mitigations.
Obsidian integration: writes generated findings and checklists to the Rollbacks folder for archival and collaboration.

Quick Start

Provide Target: deployment, commit SHA, release tag, or PR reference; Context: what went wrong or why rollback is being considered; Optional: urgency level.

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 checklist for a deployment or migration?▼

To create a rollback checklist, provide the deployment target, commit SHA, or PR reference along with context about the issue. The skill analyzes migration reversibility, API compatibility, and feature-flag dependencies to generate a prioritized, reproducible safety checklist.

What is a rollback risk assessment for multi-service environments?▼

A rollback risk assessment evaluates code changes, database migrations, and configuration updates across multi-service environments to determine reversibility, identify blockers, and categorize safety levels to minimize downtime and data risk.

How do I know if a database migration is safe to rollback?▼

To determine if a database migration is safe to rollback, the skill evaluates migration reversibility and labels the change as Safe to Rollback, Requires Caution, or Potentially Dangerous, providing actionable mitigations for each category.

Can I use feature-flags to manage deployment rollback safety?▼

Yes, feature-flag dependencies are evaluated during rollback analysis. The skill checks feature-flag compatibility to ensure that rolling back code changes or configuration updates does not cause unexpected behavior in multi-service environments.

What do I need to provide for incident response rollback analysis?▼

For incident response rollback analysis, provide the deployment target, context on what went wrong, and an optional urgency level. The skill runs parallel investigation tracks to surface blockers and documents findings for post-incident learning.

When should I not use an automated rollback checklist?▼

An automated rollback checklist may not suffice when changes are categorized as Potentially Dangerous, meaning migration reversibility is low, API compatibility is broken, or feature-flag dependencies block safe rollback without manual intervention.