Migrate Validate
- 639 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
migrate-validate is a ruflo agent skill that audits pending database migrations for foreign keys, rollback safety, and naming rules for developers who need pre-apply migration QA.
About
migrate-validate is a ruvnet/ruflo skill that reviews all pending database migrations before apply time, checking foreign key references, missing rollback SQL, destructive changes without safeguards, and naming convention violations. It uses Read, Glob, Grep, and Bash alongside claude-flow memory and agentdb pattern tools to store findings. Reach for migrate-validate in CI or pre-deploy checks when a bad migration could break production schema or block rollbacks. The skill fits teams maintaining raw SQL migration folders who want automated consistency checks instead of manual DBA review on every pull request.
- migrate-validate
Migrate Validate by the numbers
- 639 all-time installs (skills.sh)
- +6 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #602 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill migrate-validateAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 639 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you validate database migrations before applying?
Use migrate-validate for development tasks
Who is it for?
Backend engineers running SQL migration pipelines who want automated pre-apply checks for safety and rollback completeness.
Skip if: Projects without file-based migrations or teams that rely solely on live database diff tools with no pending migration queue.
When should I use this skill?
Pending migrations exist and you need FK, rollback, naming, or destructive-operation validation before merge or deploy.
What you get
Migration validation report flagging FK issues, missing down scripts, unsafe destructive ops, and naming violations.
- migration validation findings
- safety and naming issue list
By the numbers
- Covers 4 validation areas: foreign keys, rollback SQL, destructive ops, and naming
Files
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 6. Flag destructive ops -- warn on DROP TABLE, DROP COLUMN, TRUNCATE without explicit confirmation 7. Check idempotency -- verify IF EXISTS / IF NOT EXISTS is used for safety 8. Check naming -- verify table names are plural, column names are snake_case, index names follow idx_table_column convention 9. Store validation patterns -- two paths (per ruflo-cost-tracker ADR-0001 dual-path pattern):
- Pattern store (typed, recommended):
mcp__claude-flow__agentdb_pattern-storewithtype: 'migration-validation'. No namespace arg — ReasoningBank routes it. - Plain store (namespace-routable):
mcp__claude-flow__memory_store --namespace migrationsfor validation results tied to a specific migration number.
10. Report -- display: errors (must fix), warnings (should fix), info (suggestions), with file path and line number for each issue
CLI alternative
npx @claude-flow/cli@latest memory search --query "migration validation results" --namespace migrationsRelated skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Run migrate-validate for static SQL migration linting before apply instead of discovering FK or rollback failures during production migration runs.
FAQ
What does migrate-validate check?
migrate-validate reviews pending migrations for foreign key consistency, missing rollback SQL, destructive operations without safeguards, and naming convention violations. It scans migration files with Read, Glob, and Grep before apply.
When should migrate-validate run?
migrate-validate should run before applying migrations to catch issues early—broken FK references, incomplete down scripts, or unsafe schema drops. Use it in pre-merge or pre-deploy workflows for SQL migration directories.