migrate-validate

Migrate Validate

Validate all pending database migrations for correctness, safety, and adherence to best practices.

When to use

Before applying migrations to catch issues early -- foreign key references to non-existent tables, missing rollback SQL, destructive operations without safeguards, and naming convention violations.

Steps

1. Find pending migrations -- use Glob to list all migration files, cross-reference with applied history via mcp__claude-flow__memory_search --namespace migrations (or memory_list) to identify pending ones. The memory_* tool family routes by namespace; agentdb_hierarchical-* does NOT (it routes by tier), so use memory_* here.
2. Parse SQL -- use Read to load each pending .up.sql and .down.sql file and parse the SQL statements
3. Check foreign keys -- verify that all REFERENCES targets exist in the current schema or in prior migrations (both applied and pending)
4. Check NOT NULL defaults -- verify that any ADD COLUMN with NOT NULL has a DEFAULT value
5. Check rollback completeness -- verify every CREATE/ALTER in the UP file has a corresponding DROP/ALTER in the DOWN file