Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From ruflo-migrations
Create a new sequentially numbered database migration with up/down SQL files
npx claudepluginhub erfwn81/velora --plugin ruflo-migrationsHow this skill is triggered — by the user, by Claude, or both
Slash command
/ruflo-migrations:migrate-create <name><name>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a new database migration with sequential numbering and up/down SQL file pair.
Mines projects and conversations into a searchable memory palace and retrieves past work via semantic search.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
Share bugs, ideas, or general feedback.
Generate a new database migration with sequential numbering and up/down SQL file pair.
When you need to create a new database migration for schema changes such as creating tables, adding columns, creating indexes, or modifying constraints.
Glob to scan the migrations directory for existing migration files and find the highest number, then increment by 1 (zero-pad to 3 digits)<name>, choose the appropriate SQL template:
create_ -> CREATE TABLE templateadd_ -> ALTER TABLE ADD COLUMN templatedrop_ -> DROP with safety checksindex -> CREATE INDEX templateNNN_<name>.up.sql with the appropriate SQL using IF NOT EXISTS for idempotencyNNN_<name>.down.sql with the reverse operation using IF EXISTSmcp__claude-flow__agentdb_pattern-search (ReasoningBank-routed; don't pass a namespace argument — pattern-* tools ignore it).mcp__claude-flow__memory_store --namespace migrations to record the migration with number, name, status (pending), and file paths. The memory_* tool family routes by namespace; agentdb_hierarchical-* does NOT (it routes by tier working|episodic|semantic), so use memory_* here. See ruflo-agentdb ADR-0001 §"Namespace convention".npx @claude-flow/cli@latest memory store --namespace migrations --key "migration-NNN_NAME" --value '{"number": NNN, "name": "NAME", "status": "pending"}'