db-migration
Skill1 starsChanged 12 days agoMITView on GitHub
Phase 4 (data tasks). Changes SQLAlchemy models and creates a verified Alembic migration for MySQL. Use only when PLAN.md "Data changes" says a migration is needed.
24 other projects use a version of this.
Adopted by
Most recently taken up by
- ricci-labs/twisetheir own version, first seen Nov 8, 2026
- globalmpc/backendskillstheir own version, first seen Nov 8, 2026
- F3-Nation/f3-nationtheir own version, first seen Nov 2, 2026
- andidev30/the-artifacttheir own version, first seen Oct 20, 2026
- lepresk/groundworktheir own version, first seen Oct 15, 2026
- nrjdalal/inscopetheir own version, first seen Oct 13, 2026
Used with
Projects with it also use api-endpoint, git-workflow and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
tadoEngSkillapi-endpoint
Add or change a backend API endpoint on this product, keeping Pydantic as the single contract authority and regenerating the TypeScript client. Use when asked to add an endpoint, expose data to the frontend, change a request or response shape, or wire a new backend capability into a page.
Also in 4 projects that use this
Microsoft AzureSkillgit-workflow
Squad branching model: dev-first workflow with insiders preview channel
Also in 3 projects that use this
- Microsoft AzureSkill
design
Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.
Also in 3 projects that use this
AnthropicSkilldebug
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
Also in 3 projects that use this
VercelSkillagent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
- +1 more from Azure
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- dipu-bd/lightnovel-crawler★ 2.6ksame name
- lncrawl/lightnovel-crawler★ 2.6ksame name
- openmeterio/openmeter★ 2.4ksame name
- F3-Nation/f3-nation★ 210same name
- hiromaily/go-crypto-wallet★ 128same name
- nrjdalal/zerostarter★ 65same name
- xin-lai/CodeSpirit★ 56same name
- globalmpc/backendskills★ 44same name
- NicholasFlemmer/styx-app★ 31same name
- nikandr-surkov/ai-saas-starter★ 16same name
14 more not listed
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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/00-ticket-workflow.mdcCursor rule
- .cursor/rules/10-general-standards.mdcCursor rule
- .cursor/rules/20-backend-standards.mdcCursor rule
- .cursor/rules/30-frontend-standards.mdcCursor rule
- .cursor/rules/40-database-standards.mdcCursor rule
- .cursor/rules/50-testing-standards.mdcCursor rule
- backend-implementSkill
- chatSkill
- codebase-exploreSkill
- frontend-implementSkill
- gitlab-mrSkill
- implementation-planSkill
- jira-createSkill
- mr-feedbackSkill
- mr-reviewSkill
- quick-fixSkill
- run-checksSkill
- self-reviewSkill
- ticket-intakeSkill
- ticket-qaSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read PLAN.md "Data changes" and the next unticked data task.
- Very specific: line 23
Run the checker (it does upgrade → downgrade → upgrade on your LOCAL/test DB): bash .cursor/skills/run-checks/scripts/check_migration.sh …
- Very specific: line 25
Verify: output ends with MIGRATION PASS.
- Very specific: line 26
Never edit a migration that already exists on main (check_guards.sh fails if you do).
- Distinctive: line 31
Never touch Elasticsearch mappings or indices.
“Common” is measured: kept by at least 6 in 10 of the 21 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
DB migration (phase 4, data tasks)
Skip this skill if PLAN.md "Data changes → Migration" is no.
Steps
- Read PLAN.md "Data changes" and the next unticked data task. Do only that task.
- Edit or create the model in
backend/app/models/following the database standards (names, explicit lengths,DECIMALfor money, indexes on foreign keys). - Generate the migration from inside
backend/:alembic revision --autogenerate -m "<KEY> <short description>" - Open the new file in
backend/alembic/versions/. Autogenerate is often wrong. Check each item:- Only the intended changes. Delete unrelated detected diffs.
- Types, lengths,
nullableand defaults are exactly what the plan says. - NOT NULL column on an existing table has
server_default(or the plan's 3-step approach). - Index / unique / FK names follow
ix_,uq_,fk_naming. downgrade()reversesupgrade()in reverse order.- A rename or drop follows expand/contract (database standards), never in place.
- No ORM model imports inside the migration (use
opandsaonly).
- Run the checker (it does upgrade → downgrade → upgrade on your LOCAL/test DB):
bash .cursor/skills/run-checks/scripts/check_migration.shVerify: output ends withMIGRATION PASS. - Never edit a migration that already exists on main (
check_guards.shfails if you do). Create a new one. alembic headsshows 2 heads after you updated from main (main got a new migration): setdown_revisionin YOUR oldest new migration to the other head. Don't usealembic merge. Then step 5 again.- Data backfill on staging/production is NOT your job. If needed, it must be under "Human actions required" in PLAN.md. If it isn't, stop and tell the human.
- Never touch Elasticsearch mappings or indices.
- Tick the task in PLAN.md. Add to PROGRESS.md log: task, migration file name,
MIGRATION PASS.
Done when
- Every item in step 4 checked
MIGRATION PASSshown in this chatalembic headsshows exactly one head
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.