mcpField
M
migrate-validate

migrate-validate

github.com/ruvnetTesting & quality80.0k728 installsUpdated today
Repository

About migrate-validate

migrate-validate is a skill for checking pending database migrations before they are applied. It reviews schema references, rollback coverage, destructive operations, idempotency, and naming, then reports issues by severity and location.

Key features

  1. 01Finds pending migration files
  2. 02Checks foreign keys and column defaults
  3. 03Verifies rollback coverage
  4. 04Flags destructive operations
  5. 05Checks idempotency and naming conventions
  6. 06Reports issues with severity and location

Use cases

  1. 01Review migrations before applying them
  2. 02Catch missing rollback statements
  3. 03Identify unsafe schema changes

MCP support

Uses Ruflo MCP memory tools to find applied migration history and store validation patterns or results.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ruvnet/ruflo --skill migrate-validate

After installing, type/migrate-validatein Claude Code to confirm it loaded.

Details

From the project README

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__plugin_ruflo-core_ruflo__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__plugin_ruflo-core_ruflo__agentdb_pattern-store with type: 'migration-validation'. No namespace arg — ReasoningBank routes it.
    • Plain store (namespace-routable): mcp__plugin_ruflo-core_ruflo__memory_store --namespace migrations for 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 migrations

Comments

Markdown supported