db-migrate
Skill9 starsChanged 4 months agoMITView on GitHub
Generate a migration from the Drizzle schema, summarize it, and apply only after confirmation
18 other projects use a version of this.
Adopted by
Most recently taken up by
- suxrobGM/jobpilottheir own version, first seen Nov 7, 2026
- lablup/backend.aitheir own version, first seen Oct 8, 2026
- linuxfoundation/insightstheir own version, first seen Oct 8, 2026
- Ame-Al/ametheir own version, first seen Oct 8, 2026
- simstudioai/simtheir own version, first seen Oct 8, 2026
- mgiovani/cc-arsenaltheir own version, first seen Sep 25, 2026
Used with
Projects with it also use react-query-best-practices, you-might-not-need-a-callback 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.
bibektimilsina00Skillreact-query-best-practices
Audit and fix React Query usage in apps/web — enforce query key factories, signal forwarding, staleTime, and proper mutation patterns. Use when reviewing or fixing server-state code.
Also in 3 projects that use this
- bibektimilsina00Skill
you-might-not-need-a-callback
Analyze and fix useCallback anti-patterns in your code
Also in 3 projects that use this
MicrosoftSkillcleanup
Also in 3 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
- MicrosoftSkill
release
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
- +3 more from bibektimilsina00
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- simstudioai/sim★ 30ksame name
- lablup/backend.ai★ 679same name
- linuxfoundation/insights★ 288same name
- alexeykrol/claude-code-starter★ 194same name
- suxrobGM/jobpilot★ 110same name
- getsentry/abacus★ 77same name
- mgiovani/cc-arsenal★ 8same name
- mean-weasel/bullhorn★ 4same name
- pgnzbl-ux/crucible★ 4same name
- vndee/engineering-skills★ 3same name
8 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.
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 13 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
- could be automatic: a setting could enforce it
- Very specific: line 8
Run npm run db:generate to produce the migration from the current Drizzle schema.
- Distinctive: line 13
STOP and ask for explicit confirmation.
- Very specific: line 14
Only after the user confirms, run npm run db:migrate.
- Very specific: line 18
Do NOT hand-edit generated SQL, apps/api/src/db/schema.ts, or existing migration files.
- Distinctive: line 21
Do NOT apply a migration or drop data without the explicit confirmation in step 4 — schema changes are one-way doors.
“Common” is measured: kept by at least 6 in 10 of the 13 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 and apply a database migration
- Run
npm run db:generateto produce the migration from the current Drizzle schema. - Print a short human-readable summary of what changed: tables added/dropped/renamed, columns, indexes, constraints — before showing raw SQL.
- Show the generated SQL.
- STOP and ask for explicit confirmation.
- Only after the user confirms, run
npm run db:migrate.
Policy:
- Do NOT hand-edit generated SQL,
apps/api/src/db/schema.ts, or existing migration files. Schema changes flow fromauth.ts/ Drizzle schema → regenerate. - Do NOT apply a migration or drop data without the explicit confirmation in step 4 — schema changes are one-way doors.
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.