migration-safety-checklist

Name: migration-safety-checklist
Availability: InStock
Author: buchananwill

Validate database migration files for structural safety constraints.

2|Updated Mar 17, 2026

Search Tags:#checklist #rollback #database #migrations #schema #safety

Ready to run

npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill migration-safety-checklist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migration-safety-checklist
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/migration-safety-checklist
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill migration-safety-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structural constraints and safety checklists help teams ensure migrations are safe, auditable, and rollback-ready before applying changes to production databases.

Core Features & Use Cases

Enforces UP/DOWN presence or explicit irreversible mark
Validates nullable/default handling for new columns
Recommends safe index and constraint operations to minimize locks
Provides guidance for rollback documentation and production safety checks
Use Case: A team reviews a migration file to confirm it won't cause long locks or data loss before deployment.

Quick Start

Run the migration-safety-checklist against a draft migration to confirm it adheres to the safety criteria and document any required changes.

Frequently Asked Questions about migration-safety-checklist

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

FAQPage Schema

How do I check if a database migration is safe for production?▼

Database migration safety checklists enforce structural constraints on migration files to prevent data loss, requiring UP/DOWN definitions, safe nullable column additions, non-blocking index creation, and documented rollback procedures before production deployment.

What makes a database schema migration unsafe for production?▼

A database schema migration is unsafe if it lacks rollback procedures, adds columns without proper nullable or default handling, or creates blocking indexes that cause long locks and data loss during execution.

How do I ensure non-blocking index creation during database migrations?▼

To ensure non-blocking index creation, validate that your database migration file follows safe constraint operations and structural recommendations designed to minimize locks during schema changes.

Do I need a DOWN migration if my schema change is irreversible?▼

If a schema change is irreversible, you do not need a DOWN migration but must explicitly mark the migration as irreversible and provide rollback documentation to maintain production safety and auditability.

What's the best way to review a draft migration before deployment?▼

The best way to review a draft migration is to run a safety checklist against it to confirm adherence to structural criteria, validating nullable column handling, index operations, and rollback procedures before deployment.

When should I not use an automated migration safety checklist?▼

You should not rely solely on an automated migration safety checklist when handling complex data transformations or non-relational databases, as it specifically validates structural constraints for relational schema changes.