How does it handle engine-specific differences like locking behavior?

The auditor determines your database engine (PostgreSQL, MySQL, or SQLite) and version to apply specific rules. For example, it knows that adding a column with a default is safe in PostgreSQL 11+ but requires a table-locking rewrite in older versions, or that MySQL requires specialized tools like gh-ost for large table ALTERS.

Which ORMs and migration frameworks are supported?

The skill supports all major frameworks including Rails (ActiveRecord), Django, Laravel, Prisma, Drizzle, Knex, TypeORM, and Sequelize. It also audits raw SQL files and tools like Flyway or Liquibase by analyzing the DDL statements directly.

Can it detect migrations that will lock my production database?

Yes. It identifies "Locking Hazards" such as creating indexes without the CONCURRENTLY keyword in PostgreSQL or operations that trigger full table copies in MySQL. It provides specific warnings and alternative code (like a two-phase deploy strategy) to keep your database online.

Does it just find errors, or does it help me fix them?

For every flagged issue, the auditor provides a 'concrete fix.' This includes rewriting SQL for safe index creation, suggesting the correct order for adding NOT NULL constraints to populated tables, or generating the missing rollback code to ensure reversibility.

Migration Auditor

Catches dangerous database migrations before they hit production. Reviews schema changes for locking hazards, data loss, missing rollbacks, and index issues across PostgreSQL, MySQL, and SQLite.

Secure checkout via Stripe

30-day refund guarantee

Converts to your local currency at checkout

1 installSecurity scanned

Works with the AI tools you already use

+20 more

+17 agents

migration-auditor

Example session with this skill installed

I'm about to deploy a PR that drops the legacy_id column from the orders table and adds an index to the customer_id column on our Postgres 15 database. Can you review these migrations?

Read your context and instructions
Compiled the migration-auditor

Migration Audit: FAIL

[FAIL] CREATE INDEX: Missing CONCURRENTLY on "orders" (50M rows).
[WARN] DROP COLUMN "legacy_id": Confirm code isn't reading.
[FIX] Rewritten migration provided with CONCURRENTLY and two-phase drop strategy for PostgreSQL 15.

Connects securely to your tools. The creator never sees your data.

What you get

Identify table-locking hazards in heavy PostgreSQL or MySQL trafficFlag destructive schema changes that could cause permanent data lossVerify that all migration files include valid, reversible rollback scriptsDetect missing concurrent index operations to prevent downtime during deployAudit engine-specific syntax errors across multiple database dialects

About this skill

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.

How to install

Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

~30 seconds

1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.

Skills folder by agent

Click the path to copy it. Create the folder if it does not exist yet.

Reviews

No reviews yet

Be one of the first to try it. Every listed skill passes our trust checks below.

Security scanned

Passed our 8-point scan before listing

1 install

Downloaded by developers to date

30-day refund

Not a fit? Get your money back

Trust & safety