migration-checker

Review database migrations for safety, rollback capability, and zero-downtime deployment.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/physics91/claude-vibe --skill migration-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-checker
Source: https://github.com/physics91/claude-vibe/tree/main/skills/migration-checker
Command: npx skills add https://github.com/physics91/claude-vibe --skill migration-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reviews database migrations for safety, backwards compatibility, rollback capability, and zero-downtime deployment.

Core Features & Use Cases

  • Dangerous operations: flags NOT NULL adds, drop/rename columns, and type changes.
  • Rollback validation: ensures a safe rollback path and data preservation.
  • Zero-downtime patterns: demonstrates concurrent index creation and multi-step migrations.
  • Use Case: Validate a migration plan before running in production.

Quick Start

Run the migration-checker on a repository with migrations to obtain a safe, multi-step rollout plan.

Frequently Asked Questions about migration-checker

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

FAQPage Schema
How do I check if my database migrations are safe before production deployment?

Database migration safety checks review schema changes for dangerous operations like adding non-nullable columns, dropping or renaming columns, and type changes that risk data loss. This Skill audits your migrations against ORM and migration tooling such as Prisma, Alembic, TypeORM, Rails, Flyway, and Liquibase to flag risky patterns and enforce backwards compatibility, rollback capability, and zero-downtime deployment practices.

What migration patterns cause downtime and data integrity issues?

Common unsafe patterns include direct addition of non-nullable fields, unsupervised column renames and drops, concurrent constraint changes, and unbatched data transformations. Migration review identifies these patterns and enforces safer alternatives like multi-step field addition, concurrent index creation, and batched data migrations to maintain data integrity while minimizing deployment downtime.

How do I validate a rollback plan for database migrations?

Rollback validation ensures each migration step can be reversed without data loss or corruption. This Skill reviews migrations to confirm explicit rollback procedures exist, data preservation logic is sound, and the sequence supports safe reversal if production issues occur during or after deployment.

Can I use migration checking with my ORM or migration framework?

Yes. This Skill supports schema changes and data migrations across popular frameworks including Prisma, Alembic, TypeORM, Rails, Flyway, and Liquibase. It analyzes migration files to detect unsafe operations and recommend safe multi-step alternatives regardless of your tooling choice.

What's the difference between renaming a column safely versus dropping and re-adding?

Direct column renames and drops cause downtime and data loss. Safe migration patterns perform rename or restructure as multiple coordinated steps: create the new column, backfill data, update application code, then drop the old column. This maintains backwards compatibility and allows rollback without data restoration.

Do I need to rewrite migrations to pass safety checks?

Migration review identifies unsafe patterns and provides specific guidance on safe multi-step alternatives without requiring a full rewrite. You receive a rollout plan showing concurrent index creation, batched transformations, and explicit rollback procedures to apply to your existing migration strategy.