migration-safety

Review database migration safety with a structured checklist and decision tree.

Updated Jan 29, 2026

Search Tags:#checklist #database #data integrity #schema #migration #safety

Ready to run

npx skills add https://github.com/semirm-dev/agent-army --skill migration-safety

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migration-safety
Source: https://github.com/semirm-dev/agent-army/tree/main/claude/skills/migration-safety
Command: npx skills add https://github.com/semirm-dev/agent-army --skill migration-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured checklist and decision-making framework to prevent data loss, application downtime, and schema corruption during database migration processes.

Core Features & Use Cases

Comprehensive Checklist: Covers backward compatibility, dual-schema operation, down migration verification, lock time estimation, and data safety.
Decision Trees & Anti-Patterns: Offers clear guidance for complex scenarios and highlights common pitfalls to avoid.
Use Case: Before deploying a migration that alters a critical production table, use this Skill to systematically review potential risks and ensure all safety measures are in place.

Quick Start

Use the migration-safety skill to review a database migration that modifies an existing table.

Frequently Asked Questions about migration-safety

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

FAQPage Schema

How do I ensure data integrity and prevent downtime during a database schema migration?▼

To ensure data integrity during a database schema migration, use a structured checklist to verify backward compatibility, dual-schema operation, and down migration verification. This prevents data loss and application downtime by systematically reviewing potential risks and locking strategies.

What are common database migration anti-patterns when altering or dropping tables and columns?▼

Common database migration anti-patterns when altering or dropping tables include failing to account for backward compatibility, neglecting dual-schema operation, and skipping down migration verification. Reviewing these anti-patterns helps avoid schema corruption and unexpected application downtime.

How do I estimate lock time and verify rollback strategies for a production database migration?▼

Estimate lock time and verify rollback strategies for a production database migration by applying a decision tree framework that evaluates data safety and pre-deploy verification. This process ensures your down migration can safely reverse schema changes without data loss.

When do I need a dual-schema operation for backward compatibility in database migrations?▼

You need a dual-schema operation for backward compatibility in database migrations when altering or dropping critical production tables. This approach allows the application to function seamlessly across both old and new schemas during the deployment process, preventing downtime.

Does this database migration safety checklist support verifying down migrations for critical production tables?▼

Yes, this database migration safety checklist explicitly supports down migration verification for critical production tables. It provides a decision tree to validate that rollback strategies effectively reverse schema changes while maintaining data safety and preventing corruption.