Every team has a story about a migration that took down production. A column drop that wasn't actually unused. An index creation that locked a 50M-row table for 20 minutes during peak traffic. A NOT NULL constraint added to a populated table that blew up on deploy.

Migration Auditor catches these before they happen.

Point it at your migration files and it runs a 30+ point checklist covering destructive operations, locking hazards (engine-specific), missing or broken rollbacks, data integrity risks, index issues, migration ordering problems, environment-specific gotchas, and transaction safety.

It doesn't just flag problems. It writes the corrected migration code for you.

Works with Rails, Django, Laravel, Prisma, Drizzle, Knex, TypeORM, Sequelize, Flyway, Liquibase, and raw SQL. Covers PostgreSQL, MySQL/MariaDB, and SQLite with engine-specific rules (because locking behavior between them is completely different).

What it catches that generic code review doesn't:

• ADD COLUMN NOT NULL DEFAULT is dangerous on PostgreSQL < 11 but safe on 11+ (fast default). The skill checks your PG version.

• CREATE INDEX without CONCURRENTLY blocks writes on large tables. The skill flags this and rewrites it.

• MySQL ALTER TABLE copies the entire table for most DDL. On large tables, the skill recommends pt-online-schema-change or gh-ost instead.

• Rollbacks that exist but don't actually reverse the forward migration. An empty down method on a destructive migration is a failure, not a pass.

• Foreign key constraints added without NOT VALID on PostgreSQL, which locks the table for a full validation scan.

• Migrations that are safe on your 50-row dev database but will lock a 50M-row production table for minutes.

Output is a structured audit report with pass/warn/fail for each check, concrete fixes for every issue, and a recommended deploy order if you're running multiple migrations.