migration-safety
Skill0 starsChanged 25 days agoMITView on GitHub
Plan or implement a backward-compatible schema or data migration with rollout, validation, and recovery gates. Use for persistent-state changes; never run against production without explicit authorization.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Kuan-AI-com/agent-skillstheir own version, first seen Nov 15, 2026
- Mehul72/skillstheir own version, first seen Nov 8, 2026
- YiftachCohen/skillstheir own version, first seen Nov 3, 2026
- kapadias/nonnatheir own version, first seen Oct 1, 2026
- novatic-cu/nova-skillstheir own version, first seen Sep 20, 2026
- dennisrongo/claude-skillstheir own version, first seen Aug 16, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- dennisrongo/claude-skills★ 1same name
- Mehul72/skills★ 1same name
- novatic-cu/nova-skills★ 1same name
- YiftachCohen/skills★ 1same name
- kapadias/nonna★ 0same name
- Kuan-AI-com/agent-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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- acceptance-qaSkill
- architecture-reviewSkill
- bug-fix-verificationSkill
- dependency-upgradeSkill
- docs-syncSkill
- idea-to-scopeSkill
- implementation-planSkill
- independent-reviewSkill
- performance-investigationSkill
- pull-request-handoffSkill
- release-checkpointSkill
- root-cause-investigationSkill
- security-reviewSkill
- surgical-changeSkill
- test-gap-auditSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
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 15
Stop before production execution, irreversible backfill, table drop, or deletion unless scope, environment, backup/recovery posture, and …
“Common” is measured: kept by at least 6 in 10 of the 4 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
Migration safety
A migration is a compatibility transition, not only a SQL file.
- Identify source and destination schemas, data owners, writers/readers, deploy topology, retention obligations, and expected data volumes when known.
- State invariants: no lost records, compatibility with old and new application versions, stable identifiers, constraints, and permitted downtime or dual-write periods.
- Design a staged sequence where appropriate: expand, deploy compatible readers/writers, backfill, verify, then contract in a later authorized window. Do not force this pattern when a simpler transaction is genuinely safe.
- Specify replayability, batch size, lock exposure, idempotency, validation queries, monitoring, and failure/rollback semantics. A reversible schema change does not automatically reverse changed data.
- For authorized local implementation, edit only scoped migration code and tests. Test on disposable or sanitized representative data, including old/new version combinations if practical.
- Stop before production execution, irreversible backfill, table drop, or deletion unless scope, environment, backup/recovery posture, and authority are explicit. Do not silently perform production operations.
Output
Invariants, ordered rollout, compatibility window, verification queries/checks, stop/rollback plan, unverified assumptions, and exactly what was executed where.
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.

