mcpbeat

Database Migrations

hoangnguyen0403/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.

1k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
536
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill database-migrations

What comes with it

3 204 bytes besides the instruction
evals/evals.json
references/migration-safety-checklist.md

The instruction itself

6 sections, as written by the author

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
  • Migration Safety Checklist

How to use it

Copy the folder

Take hoangnguyen0403/database-migrations from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.