safe-migration
Skill0 starsChanged 13 days agoMITView on GitHub
Plan and execute a controlled migration of code, schemas, frameworks, or configuration while preserving a rollback path. Use when changing formats, APIs, databases, runtimes, or major dependencies.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- electronx/wiredkits-freetheir own version, first seen Oct 25, 2026
- Ionate-Technologies/indium-agentkittheir own version, first seen Oct 20, 2026
- Indium-AI-Labs/indium-agentkittheir own version, first seen Oct 11, 2026
- ritmillio/skillstheir own version, first seen Aug 23, 2026
- gastonsalg/claude-skillstheir own version, first seen Nov 28, 2025
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- Indium-AI-Labs/indium-agentkit★ 18same name
- Ionate-Technologies/indium-agentkit★ 17same name
- electronx/wiredkits-free★ 5same name
- gastonsalg/claude-skills★ 0same name
- ritmillio/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-skill-auditSkill
- api-contract-checkSkill
- build-rescueSkill
- change-narrativeSkill
- context-handoffSkill
- data-quality-gateSkill
- dataset-workshopSkill
- dependency-careSkill
- docs-syncSkill
- experiment-ledgerSkill
- failure-forensicsSkill
- model-diff-reviewSkill
- model-eval-designSkill
- multi-agent-crosscheckSkill
- parallel-task-designSkill
- performance-proofSkill
- release-readinessSkill
- repo-scoutSkill
- research-evidence-mapSkill
- review-lensSkill
- security-surfaceSkill
- spec-firstSkill
- sql-integrity-checkSkill
- test-driven-changeSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Prefer staged migration: add compatible support, backfill or dual-write if required, verify parity, switch readers, monitor, then remove …
- Very specific: line 14
Create dry-run or preview mode for any bulk operation.
- Distinctive: line 15
Add invariants and reconciliation checks: row counts, checksums, referential integrity, schema validity, and representative queries.
- Distinctive: line 16
Test interruption and rerun behavior.
- Distinctive: line 17
Document deployment order, feature flags, operational signals, rollback trigger, and cleanup steps.
- Distinctive: line 23
Never run a destructive or production migration without explicit authorization and a verified backup/restore path.
- Distinctive: line 24
Never assume rollback is safe after irreversible data transformation.
- Distinctive: line 25
Keep implementation and irreversible cleanup in separate steps whenever practical.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Safe Migration
Procedure
- Define the source state, target state, users affected, deadline, data volume, downtime constraints, and success criteria.
- Inspect all readers/writers, external consumers, scheduled jobs, and hidden operational assumptions.
- Classify the migration as reversible, forward-only, or data-destructive. Design a backup and rollback plan before implementation.
- Prefer staged migration: add compatible support, backfill or dual-write if required, verify parity, switch readers, monitor, then remove old support in a separate approved step.
- Create dry-run or preview mode for any bulk operation. Report the records/files/resources that would change before applying them.
- Add invariants and reconciliation checks: row counts, checksums, referential integrity, schema validity, and representative queries.
- Test interruption and rerun behavior. Ensure the migration is idempotent or clearly prevents accidental repeated execution.
- Document deployment order, feature flags, operational signals, rollback trigger, and cleanup steps.
Deliverable
Provide a phased checklist, compatibility matrix, preflight checks, rollback plan, and exact verification evidence.
Boundaries
- Never run a destructive or production migration without explicit authorization and a verified backup/restore path.
- Never assume rollback is safe after irreversible data transformation.
- Keep implementation and irreversible cleanup in separate steps whenever practical.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.