new-migration
Skill1 starsChanged 5 months agoMITView on GitHub
Generate a new Alembic migration from current model changes and review it
6 other projects use a version of this.
Adopted by
Most recently taken up by
- violacase/Nuxt4-testtheir own version, first seen Oct 13, 2026
- fleetdm/fleettheir own version, first seen Oct 8, 2026
- CodeWithCJ/SparkyFitnesstheir own version, first seen Oct 8, 2026
- tstephx/book-mcp-servertheir own version, first seen Aug 19, 2026
- sebastiandev/ateliertheir own version, first seen Aug 19, 2026
- TheAstrelo/Claude-Pipelinetheir own version, first seen Jul 26, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- fleetdm/fleet★ 7.2ksame name
- CodeWithCJ/SparkyFitness★ 6.7ksame name
- TheAstrelo/Claude-Pipeline★ 44same name
- sebastiandev/atelier★ 8same name
- tstephx/book-mcp-server★ 1same name
- violacase/Nuxt4-test★ 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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- db-migrateSkill
- db-resetSkill
- fastapiSkill
- supabase-postgres-best-practicesSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
0
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
- Very specific: line 11
Make sure the intended change is reflected in apps/api/src/app/models.py first — Alembic autogenerate diffs the ORM models against the live …
“Common” is measured: kept by at least 6 in 10 of the 6 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
Generate a new database migration for: $ARGUMENTS
Steps:
- Make sure the intended change is reflected in
apps/api/src/app/models.pyfirst — Alembic autogenerate diffs the ORM models against the live database. - Generate the migration:
make revision m="$ARGUMENTS" - Open the newly created file under
apps/api/migrations/versions/and review it carefully:- Does
upgrade()capture the full intent? Autogenerate misses server defaults, enum value changes, index renames, and data backfills. - Is
downgrade()correct and reversible? - For column additions on a non-empty table, is the column nullable or given a server default?
- Does
- Apply it with
make migrateand confirm it succeeds. - Summarize what the migration does and any manual edits you made to the generated file.
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.