migration-guard
Skill2 starsChanged 2 months agoMITView on GitHub
Reviews a database migration before it ships to make sure it is safe — reversible, non-destructive, and backward-compatible — following the project's database conventions. Use this whenever you create, review, or approve a schema or data migration (e.g. "check this migration", "is this migration safe to deploy?").
2 other projects use a version of this.
Adopted by
Most recently taken up by
- brayandiazc/project-starter-template-es-aitheir own version, first seen Sep 7, 2026
- 0xmortuex/claude-code-skillstheir own version, first seen Jul 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- brayandiazc/project-starter-template-es-ai★ 15same name
- 0xmortuex/claude-code-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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- changelogSkill
- commitSkill
- configure-repoSkill
- copywritingSkill
- design-system-auditSkill
- i18n-paritySkill
- identitySkill
- instantiateSkill
- new-adrSkill
- new-specSkill
- open-issueSkill
- open-prSkill
- port-changeSkill
- prototypeSkill
- releaseSkill
- seo-auditSkill
- update-templateSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Verify reversibility: there is a working down/rollback path, or the change is explicitly documented as irreversible with justification.
- Very specific: line 14
Check for data loss: dropping columns/tables, narrowing types, or adding a NOT NULL column without a default/backfill.
- Distinctive: line 16
Check backward compatibility for zero-downtime deploys: can old and new code run against the new schema during rollout?
- Distinctive: line 19
Check locking / large tables: operations that rewrite or long-lock big tables (e.g.
- Distinctive: line 29
Do NOT run the migration. Do NOT loosen the project's database rules to make a migration pass — fix the migration instead.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Review the migration the user points to (or the one in the current diff) for safety.
- Read
docs/conventions/database.mdfor the project's migration rules (naming, reversibility, index strategy, allowed column types) anddocs/architecture/database.mdfor the current data model it touches. - Verify reversibility: there is a working
down/rollback path, or the change is explicitly documented as irreversible with justification. - Check for data loss: dropping columns/tables, narrowing types, or adding a
NOT NULLcolumn without a default/backfill. Flag any destructive step. - Check backward compatibility for zero-downtime deploys: can old and new code run against the new schema during rollout? Prefer expand → migrate → contract over a single breaking change.
- Check locking / large tables: operations that rewrite or long-lock big tables (e.g. adding a non-null column, certain index builds). Suggest the safe variant for the project's database.
- Confirm a rollback plan and that the migration is idempotent / safe to retry where the tooling allows.
Output: a short verdict (safe / unsafe), the specific risks found, and the minimal
changes to make it safe. If the decision is significant (e.g. an irreversible
migration), recommend recording an ADR in docs/decisions/.
Do NOT run the migration. Do NOT loosen the project's database rules to make a migration pass — fix the migration instead.
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.

