Migration Gate — will this database migration lock your table?

Paste a database migration — raw SQL, a Django migration, a Kysely or Drizzle file, a golang-migrate pair or a Prisma migration.sql — and get a production-safety audit before you run it: a safe / caution / block verdict judged against your table size and your downtime budget, every statement classified by the lock it takes and what real traffic cannot do while it runs, a ten-check status table, prioritized findings each with corrected SQL, an expand-contract rollout with the deploy gate between every step, the whole migration rewritten to be safe, a rollback path and the queries that prove each phase landed. A free in-browser prescan splits the paste into real statements — respecting quotes, dollar-quoted bodies and comments — classifies each by lock level, and flags NOT NULL without a default, non-concurrent index builds, unbatched backfills, constraints added without NOT VALID and more, before you spend anything; the rewritten migration is then re-analysed by that same prescan, so the page verifies the fix rather than repeating the claim. Derived from the @affaan-m/database-migrations agent skill; not affiliated with its author, nor with the PostgreSQL or MySQL projects.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.