biggish
SolidExplains the migration procedure in depth. Use when the user runs a data migration or mentions migration steps.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- ncoevoet
- Repository
- ncoevoet/claude-markdown-health-check
- Created
- 2 months ago
- Last Updated
- 3 days ago
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
migration-planner
Use for migration, replatform, schema change, backfill, dual write, shadow read, cutover, rollback, kill switch, expand contract, big bang, online migration, blue green, framework upgrade, cloud migration, zero downtime change. Produces a phased runbook, dual write plan, shadow read and backfill spec, cutover checklist, kill switch wiring, and a post migration cleanup ticket. Sequences destructive changes so production keeps working at every step, each phase ships independently, and every step is reversible until the cutover. Do not invoke for small in place changes that fit one deploy with no data reshape and no consumer coordination; that is a normal change, not a migration.
migrate
Run a mechanical migration across a whole codebase — discover every call site, transform each in isolation, verify per-site, and gate on a clean sweep (no old-pattern remnants) with the suite green. For API/dependency/pattern/framework migrations.
add-db-migration
Use when a ticket requires a database schema change — a new table/column, an index, a constraint, or a backfill. Invoke for "add a migration for X", "alter the schema", or any change to the persisted data model. Schema changes are high-risk; treat them carefully.