/database-migrations

Plan additive, zero-downtime schema migrations with rollout, backfill, and rollback awareness. Use when renaming columns, backfilling data, or shipping risky database changes.

hoangnguyen0403@hoangnguyen0403

GitHub

From plugin

agent-skills-standard

538200 skills1 MCP

Install

$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill database-migrations --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/database-migrations

Context preview

The summary Claude sees to decide when to auto-load this skill.

Plan additive, zero-downtime schema migrations with rollout, backfill, and rollback awareness. Use when renaming columns, backfilling data, or shipping risky database changes.

SKILL.md

database-migrations.SKILL.md

name: database-migrations
description: Plan additive, zero-downtime schema migrations with rollout, backfill, and rollback awareness. Use when renaming columns, backfilling data, or shipping risky database changes.
metadata:
  triggers:
    files:
    - '**/migrations/*.sql'
    - 'prisma/schema.prisma'
    - '**/*.entity.ts'
    keywords:
    - migration
    - backfill
    - rollout
    - rename column
    - zero downtime

Database Migrations

Priority: P0 (CRITICAL)

Use expand -> backfill -> contract for risky changes.

Rules

Ship additive schema first.
Backfill with resumable logic and visibility.
Flip reads/writes only after new shape is populated.
Drop old columns or indexes in a later safe step.

Verify

[ ] Migration can run without taking the app offline.
[ ] Backfill ownership, batching, and monitoring are defined.
[ ] Rollback or pause strategy exists.
[ ] Old and new code paths can coexist during rollout.

Anti-Patterns

**No destructive one-shot rename**: expand and migrate first.
**No hidden backfill**: long data moves need explicit plan and observability.
**No app deploy coupling by accident**: schema and code rollout order must be clear.