Back to catalog / Developer tools
Database schema and data migration
Plan staged ORM/schema changes with validation and rollback paths.
Skills
Confirm database engine, ORM, data volume, and compatibility window before drafting a migration. For zero-downtime renames, use expand–migrate–contract: add compatible columns, backfill in batches, verify counts/checksums, then remove old fields only after the new version is stable. Bound locks and duration for transactional migrations; use checkpoints/idempotent batches for large moves and rehearse restore on a backup/staging system.
Permissions
Prerequisites
- Needs database/ORM versions, schema, backup, and change window; prepare staging data first.
Permissions
- May inspect migrations and draft schema/data changes; running them writes the database and needs explicit production approval.
Limitations
Rollback may not recover lost data; test dual writes, locks, replication lag, and restore in advance.
Pinned upstream source
- Repository
- wshobson/agents
- File path
- plugins/framework-migration/skills/database-migration/SKILL.md
- Pinned commit
46891e7e60da0e52baf1050b7b6391b64e84c6d9- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Prisma · TypeORM · Sequelize · SQL database CLI
Main topic
Take a coding Agent change from context to verification