Database migrations
Skill kimtth/agent-skill-100-lines-or-less/skills/database-migrations
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill database-migrationsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when: write and apply schema migrations safely without downtime or data loss.
SKILL.md
1.0 KB, 205 tokens by cl100k_base, as published. Nobody here has run it
Goal: schema changes that are reversible, ordered, and safe in production.
Use for:
- adding, altering, or dropping columns and tables
- coordinating schema and code deploys
- avoiding locks and data loss on large tables
Workflow:
- Make each migration small, ordered, and version-controlled.
- Prefer additive changes; split risky changes into steps.
- Use expand-then-contract for renames and type changes.
- Backfill data in batches to avoid long locks.
- Deploy code that tolerates both old and new schema.
- Verify on a production-like dataset before rollout.
Expand/contract:
- add new column/table, deploy dual-write code
- backfill, then switch reads
- remove old column only after nothing uses it
Rules:
- never edit an already-applied migration; add a new one
- avoid long-held locks on large tables
- make migrations reversible or document the rollback
- test against realistic data volume, not an empty schema
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.