migration-audit

Audit database migrations for safety risks using static checks M1-M8.

3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/marcoguillermaz/claude-dev-kit --skill migration-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-audit
Source: https://github.com/marcoguillermaz/claude-dev-kit/tree/main/packages/cli/templates/tier-m/.claude/skills/migration-audit
Command: npx skills add https://github.com/marcoguillermaz/claude-dev-kit --skill migration-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams detect risky migrations early by analyzing migration files for patterns that can cause data loss, downtime, or schema drift.

Core Features & Use Cases

  • Static safety checks across migration files (M1–M8) to flag lock-heavy DDL, non-reversible changes, unsafe backfills, and constraint sequencing.
  • Framework-aware scanning for Prisma, Drizzle, Supabase CLI, and raw SQL migrations, with stepwise discovery and ordering verification.
  • Backlog-ready reporting with executive summary and recommended fixes to support safe deployment.

Quick Start

Run the migration-audit tool against your migrations to generate a comprehensive risk report.

Frequently Asked Questions about migration-audit

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

FAQPage Schema
How do I audit database migrations for unsafe SQL patterns?

To audit database migrations, run static safety checks that scan migration files for lock-heavy DDL, non-reversible changes, and unsafe backfills to prevent downtime and data loss.

What are common risky migration patterns that cause database downtime?

Risky migration patterns include lock-heavy DDL operations, non-reversible changes, unsafe backfills, and improper constraint sequencing, all of which can cause schema drift or database downtime.

Does the migration audit work with Drizzle and Prisma migration files?

Yes, the migration audit works with Drizzle, Prisma, Supabase CLI, and raw SQL migration files, performing framework-aware scanning and ordering verification across your project.

Can I scan a specific range of Supabase migrations instead of the whole project?

Yes, you can target a specific range of migrations or scan all migration files across your project, receiving backlog-ready findings and an executive summary of identified risks.

Do I need network access to run a database migration safety check?

No, the database migration safety check operates entirely without external network access, using static analysis to apply safety checks and output recommended fixes.