rollback

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.

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.

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.

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.

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.

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.