write-migration
Skill1.1k starsChanged 59 days agoMITView on GitHub
Write or edit an Alembic migration safely against production data and constraints. Use for migrations, schema constraints, indexes, or column defaults.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ctxr-dev/llm-wiki-memorytheir own version, first seen Aug 4, 2026
- rezendefabio/financas-labtheir own version, first seen May 30, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ctxr-dev/llm-wiki-memory★ 131same name
- rezendefabio/financas-lab★ 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 repository9 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- check-prodSkill
- debug-deploySkill
- gh-stackSkill
- query-prod-dbSkill
- reset-prod-submissionsSkill
- review-pr-commentsSkill
- review-terraformSkill
- ship-itSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read the migration guide, including its safety rules, and inspect adjacent migrations and scripts/lint_migration_sql.py.
- Distinctive: line 12
Write the migration and add coverage for populated-data upgrades and the downgrade behavior, following the documented concurrent-friendly …
- Distinctive: line 14
Run the migration SQL lint and relevant migration tests from the guide.
- Distinctive: line 15
Follow Quality Gates for the full pre-push gate.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Write Migration
- Read the migration guide, including its safety
rules, and inspect adjacent migrations and
scripts/lint_migration_sql.py. - Determine whether this requires a new revision or whether the existing revision is still safe to edit under the guide's immutability rules.
- Write the migration and add coverage for populated-data upgrades and the downgrade behavior, following the documented concurrent-friendly patterns.
- Run the migration SQL lint and relevant migration tests from the guide. Follow Quality Gates for the full pre-push gate.
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.