migration-design
Skill0 starsChanged 7 months agoMITView on GitHub
Plan schema or data migrations with rollout, backfill, compatibility, and rollback in mind before changing production persistence.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when a change touches existing data, schema evolution, backfill logic, or rollout safety across versions.
- Distinctive: line 21
avoid rollout plans that break mixed-version deployments
- Distinctive: line 27
Check whether the system must support mixed old and new code during rollout.
- Distinctive: line 34
Call out locking, batch size, retry, and observability concerns.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Migration Design
Use this skill when a change touches existing data, schema evolution, backfill logic, or rollout safety across versions.
Read First
- current schema and migration history
- deployment and rollback constraints
- data volume and downtime tolerance
docs/reference/requirements.mdandharness/state.mdif they existharness/history.mdif it exists
Goals
- make the migration sequence safe and explicit
- separate schema change from data backfill when needed
- avoid rollout plans that break mixed-version deployments
- capture rollback and repair paths before implementation
Steps
- Define what data shape is changing and why.
- Check whether the system must support mixed old and new code during rollout.
- Split the change into phases:
- additive schema
- dual-write or compatibility phase if needed
- backfill
- read-path switch
- cleanup
- Call out locking, batch size, retry, and observability concerns.
- Define rollback or stop-the-rollout conditions.
- Recommend the safest migration sequence with trade-offs.
Output
Report:
- migration goal
- phased rollout plan
- compatibility strategy
- backfill and observability notes
- rollback path
- risks
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codex/AGENTS.mdAGENTS.md
- claude/CLAUDE.mdCLAUDE.md
- backend-refactorSkill
- buildSkill
- discussSkill
- docSkill
- frontend-designSkill
- frontend-refactorSkill
- low-altitude-interviewerSkill
- pdfSkill
- repo-bootstrapSkill
- skill-maintenanceSkill
- tdd-executionSkill
- architecture-guardrailsSkill
- closed-loop-testingSkill
- harness-marathonSkill
- task-harnessSkill
- api-designSkill
- architecture-designSkill
- brainstormSkill
- codex-record-retrospectiveSkill
- database-designSkill
- integration-designSkill
- map-codebaseSkill
- observability-designSkill
- planSkill
- query-optimizationSkill
- scalability-checkSkill
- service-boundary-reviewSkill
- api-change-checkSkill
- browseSkill
- bugfix-verificationSkill
- debugSkill
- incident-debugSkill
- performance-investigationSkill
- qaSkill
- reviewSkill
- security-reviewSkill
- verifySkill
- release-checkSkill
- shipSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.