Skill

migrate-validate

Validate pending migrations for foreign key consistency, rollback safety, and best practices

npx claudepluginhub erfwn81/velora --plugin ruflo-migrations

Popularity

Shared by

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/ruflo-migrations:migrate-validate

User invocable

Model invocable

Inline context

Default effort

Tool Access

This skill is limited to the following tools:

ReadGlobGrepBashmcp__claude-flow__memory_searchmcp__claude-flow__memory_listmcp__claude-flow__memory_storemcp__claude-flow__agentdb_pattern-storemcp__claude-flow__agentdb_semantic-route

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

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

SKILL.md

36 lines · ~636 tokens

Similar Skills

mempalace

55.4k

Mines projects and conversations into a searchable memory palace and retrieves past work via semantic search.

mempalace

payload

42.5k

Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.

11 files

payload

vector-database-engineer

37.9k

Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.

antigravity-bundle-data-engineering

Stats

LanguageTypeScript

Parent stars0

MaintenanceGood

Last CommitMay 9, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

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

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.

Parse SQL -- use Read to load each pending .up.sql and .down.sql file and parse the SQL statements

Check foreign keys -- verify that all REFERENCES targets exist in the current schema or in prior migrations (both applied and pending)

Check NOT NULL defaults -- verify that any ADD COLUMN with NOT NULL has a DEFAULT value

Check rollback completeness -- verify every CREATE/ALTER in the UP file has a corresponding DROP/ALTER in the DOWN file

Flag destructive ops -- warn on DROP TABLE, DROP COLUMN, TRUNCATE without explicit confirmation

Check idempotency -- verify IF EXISTS / IF NOT EXISTS is used for safety

Check naming -- verify table names are plural, column names are snake_case, index names follow idx_table_column convention

Store validation patterns -- two paths (per ruflo-cost-tracker ADR-0001 dual-path pattern):

Pattern store (typed, recommended): mcp__claude-flow__agentdb_pattern-store with type: 'migration-validation'. No namespace arg — ReasoningBank routes it.
Plain store (namespace-routable): mcp__claude-flow__memory_store --namespace migrations for validation results tied to a specific migration number.

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