database-migrations
Database migration planning and review workflow. Use when creating, altering, renaming, backfilling, indexing, or deleting database schema or data, especially when zero-downtime, rollback, large tables, or production safety matters.
Works with
--- name: database-migrations description: Database migration planning and review workflow. Use when creating, altering, renaming, backfilling, indexing, or deleting database schema or data, especially when zero-downtime, rollback, large tables, or production safety matters. license: MIT --- # Database Migrations Use this skill when database structure or persisted data changes. ## What to Apply - Separate schema changes from data backfills when risk or scale is meaningful. - Prefer expand-contract migrations for renames, type changes, and destructive changes. - Check locks, large-table behavior, default values, indexes, and rollback strategy. - Treat deployed migrations as immutable. - Require tests or dry runs that match the project migration tooling. ## Reference Files - [ai-agent-standards/prompts/sample-use-cases/database-migration.md](../../ai-agent-standards/prompts/sample-use-cases/database-migration.md) - [ai-agent-standards/engineering-practices/TESTING_STANDARDS.md](../../ai-agent-standards/engineering-practices/TESTING_STANDARDS.md) - [ai-agent-standards/risk-management/escalation-workflow.md](../../ai-agent-standards/risk-management/escalation-workflow.md) ## Output Expectation State the migration sequence, rollback or forward-fix plan, and verification steps before touching production data.
More Database skills
azure-upgrade
microsoft/azure-skills
Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-database-setup
prisma/skills
Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on "configure postgres", "connect to mysql", "setup mongodb", "sqlite setup".
