Skip to content
Back to skills

Database Migrations

ASecurity

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

  • 549 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 5, 2026
developmentsqldatabase

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 5, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Database Migrations?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Database Migrations
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hoangnguyen0403-database-migrations-agent-skills-standard/badge)](https://www.skillsdirectory.com/skills/hoangnguyen0403-database-migrations-agent-skills-standard)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
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.

## References

- [Framework Map](../references/framework-map.md)
- [Migration Safety Checklist](references/migration-safety-checklist.md)

Files in this skill

  • SKILL.md1.3 KB
  • evals/evals.json1023 B
  • references/migration-safety-checklist.md2.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…