Drizzle
kurealnum/dotfiles
Drizzle ORM schema and database guide. An agent skill from kurealnum/dotfiles.
Guide for making database schema changes in Platypus using Drizzle ORM — editing the schema, pushing to a dev database, and generating the migration that ships.
Install Database Schema Changes
$ npx skills add willdady/platypus --skill database-schema-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install willdady/platypus database-schema-changes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/database-schema-changes .claude/skills/database-schema-changes && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "database-schema-changes" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/database-schema-changes into .claude/skills/database-schema-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-schema-changes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/willdady/platypus/tree/main/.agents/skills/database-schema-changesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add willdady/platypus --skill database-schema-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install willdady/platypus database-schema-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/database-schema-changes .agents/skills/database-schema-changes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "database-schema-changes" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/database-schema-changes into .agents/skills/database-schema-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-schema-changes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add willdady/platypus --skill database-schema-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install willdady/platypus database-schema-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/database-schema-changes .cursor/skills/database-schema-changes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "database-schema-changes" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/database-schema-changes into .cursor/skills/database-schema-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-schema-changes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/willdady/platypus.git --path .agents/skills/database-schema-changes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add willdady/platypus --skill database-schema-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install willdady/platypus database-schema-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/database-schema-changes .gemini/skills/database-schema-changes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "database-schema-changes" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/database-schema-changes into .gemini/skills/database-schema-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-schema-changes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install willdady/platypus database-schema-changesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add willdady/platypus --skill database-schema-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/database-schema-changes .github/skills/database-schema-changes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "database-schema-changes" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/database-schema-changes into .github/skills/database-schema-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-schema-changes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add willdady/platypus --skill database-schema-changes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install willdady/platypus database-schema-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/database-schema-changes .opencode/skills/database-schema-changes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "database-schema-changes" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/database-schema-changes into .opencode/skills/database-schema-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-schema-changes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
database-schema-changes- GitHub stars
- 116
- Token cost
- ~527 tokens
- SKILL.md length
- 272 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guide for making database schema changes in Platypus using Drizzle ORM — editing the schema, pushing to a dev database, and generating the migration that ships.
- Works in 3 steps: Edit the schema — the backend's Drizzle… → Push it to your dev database. Needs pnpm… → Generate the migration. Production…
- Tasks that involve Database schema design
- SKILL.md covers Steps, Data changes and Auth tables
- Calls pnpm and git
What it does
Database Schema Changes is an agent skill from willdady/platypus. Guide for making database schema changes in Platypus using Drizzle ORM — editing the schema, pushing to a dev database, and generating the migration that ships.
Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases, covering Database schema design. It works with Drizzle ORM. The repository describes itself as: Self-hosted AI Agents for your whole team — on your infrastructure, your models, around the clock. The licence is MIT.
When your agent uses it
- Tasks that involve Database schema design
Example prompts
- “/database-schema-changes”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Edit the schema — the backend's Drizzle schema module, where the tables
- Push it to your dev database. Needs pnpm dev up, since the push talks
- Generate the migration. Production applies numbered .sql migrations,
What it can do on your machine
Read from SKILL.md and the folder at commit 2147848. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpmgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Database Schema Changes loads about 527 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 272 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from willdady/platypus at commit 2147848, republished under its MIT licence (© willdady). 272 words, ~527 tokens.
Download SKILL.mdSave it as
.claude/skills/database-schema-changes/SKILL.md (or your agent's skills folder).- name
- database-schema-changes
- description
- Guide for making database schema changes in Platypus using Drizzle ORM — editing the schema, pushing to a dev database, and generating the migration that ships.
Database Schema Changes
Push is for your machine; generate is what ships. Both, every time. A push with no generate leaves a dev database that works and a production deploy that never receives the change — and nothing local tells you, because your own database is already correct.
Steps
Edit the schema — the backend's Drizzle schema module, where the tables are declared.
Push it to your dev database. Needs
pnpm devup, since the push talks to a live Postgres:bash pnpm drizzle-kit-pushGenerate the migration. Production applies numbered
.sqlmigrations, not your schema file, so this is the step that carries the change out of your machine:bash pnpm drizzle-kit-generate
Done when git status shows three new or modified artefacts beside your
schema edit: a numbered .sql migration, its snapshot, and an appended journal
entry. All of them are committed, in the same commit as the schema change.
Data changes
Generate writes DDL — it reads your schema and diffs it. A backfill, a re-shaping of existing rows, or anything else that needs to reason about data is yours to write into the generated migration by hand.
Dev never runs it: the push flow applies DDL only and skips migration files entirely, so a hand-written backfill is invisible until production. Apply the equivalent change to your own database by hand and say so on the PR.
Auth tables
better-auth owns the auth tables — do not hand-edit that generated schema. When you change the auth configuration, regenerate it, then treat the result as a normal schema change and continue from step 2:
pnpm --dir apps/backend dlx @better-auth/cli@latest generate \
--config ./src/auth.ts --output ./src/db/auth-schema.ts --yes(The paths inside that command are arguments the CLI needs, not references to look up.)
© willdady, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/database-schema-changes of willdady/platypus.
Open the folder on GitHubat commit 2147848
Compare with similar skills
Database Schema Changes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Database Schema Changes this skillwilldady/platypus | 116 | — | ~527 | Automated safety check: Pass | MIT | |
| Drizzlekurealnum/dotfiles | 290 | — | ~1.3k | Automated safety check: Pass | None | |
| Drizzle Migration Safety on Neonsuperset-sh/superset | 15k | — | ~2k | Automated safety check: Notes | Custom licence | |
| Drizzle Erdhiroppy/mf-dashboard | 418 | — | ~627 | Automated safety check: Pass | MIT | |
| Drizzle DatabaseChatbotXIO/ChatbotX | 878 | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Drizzle Schema Style Guidelobehub/lobehub | 83k | — | ~4.1k | Automated safety check: Pass | Custom licence |
Similar skills
Drizzle Migration Safety on Neon
superset-sh/superset
Generates a Drizzle migration on a fresh Neon branch and runs a production-safety checklist for table sizes, lock order and load rehearsal before the PR opens.
Drizzle Erd
hiroppy/mf-dashboard
A skill your agent uses when needing to visualize database schema, generate ERD diagrams from Drizzle ORM schemas, or understand table relationships
Drizzle Database
ChatbotXIO/ChatbotX
Work with Drizzle ORM database schema, migrations, relations, and queries in PostgreSQL.
Drizzle Schema Style Guide
lobehub/lobehub
Style guide for Drizzle ORM schemas and queries in LobeHub: file layout, naming, timestamp helpers, primary keys, indexes, relations and inferred types.
Drizzle Orm Expert
davila7/claude-code-templates
Expert in Drizzle ORM for TypeScript — schema design, relational queries, migrations, and serverless database integration.
More from willdady/platypus
API Conventions
willdady/platypus
Response-body conventions for the Platypus backend API — the error key for failures, the message key for 2xx status messages, and when to throw a typed error instead of returning a response.
Platypus Tools
willdady/platypus
Platypus tools and tool sets — writing a tool, contributing a tool set from a plugin, scoping tools to a workspace, sharing a tool across sets, chat icons, and custom tool UI.
Add API Endpoint
willdady/platypus
Guide for adding new API endpoints to the Platypus backend using Hono.js — routing, tenant scoping middleware, validation, and database access.
Docs Audit
willdady/platypus
Audit one section of the docs content against the code, and report what is wrong, stale, fragile, off-voice, or missing.
Form Conventions
willdady/platypus
Post-save conventions for Platypus frontend forms — where a save lands the user, and what the submit button is called.
Pre Release Check
willdady/platypus
The final gate before a release is cut — go green, reconcile the release PR against what actually landed, sweep what CI can't see, check the roadmap and ADR statuses, optionally deep-review, then…
Related
Works with
Categories
Questions about Database Schema Changes
What does Database Schema Changes do?
Guide for making database schema changes in Platypus using Drizzle ORM — editing the schema, pushing to a dev database, and generating the migration that ships. Database Schema Changes is an agent skill from willdady/platypus. Guide for making database schema changes in Platypus using Drizzle ORM — editing the schema, pushing to a dev database, and generating the migration that ships.
When should I use Database Schema Changes?
Database Schema Changes fits situations like: tasks that involve Database schema design.
How do I install Database Schema Changes in Claude Code?
Run `npx skills add willdady/platypus --skill database-schema-changes -a claude-code`. Or copy the skill folder (.agents/skills/database-schema-changes in willdady/platypus) into .claude/skills/database-schema-changes in your project. Claude Code loads it when a task matches its description.
How do I install Database Schema Changes in Codex?
Run `npx skills add willdady/platypus --skill database-schema-changes -a codex`. Or copy the skill folder (.agents/skills/database-schema-changes in willdady/platypus) into .agents/skills/database-schema-changes in your project. Codex loads it when a task matches its description.
Can I use Database Schema Changes in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add willdady/platypus --skill database-schema-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/database-schema-changes, .gemini/skills/database-schema-changes, .github/skills/database-schema-changes and .opencode/skills/database-schema-changes in your project.
What does Database Schema Changes need to run?
Going by SKILL.md and its folder, Database Schema Changes needs the command-line tools its instructions call (pnpm and git).
Does Database Schema Changes access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Database Schema Changes safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Database Schema Changes use?
Database Schema Changes is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Database Schema Changes use?
About 527 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Database Schema Changes?
Skills that share tags, products or a category with Database Schema Changes: Drizzle (kurealnum/dotfiles, 290 stars), Drizzle Migration Safety on Neon (superset-sh/superset, 15k stars), Drizzle Erd (hiroppy/mf-dashboard, 418 stars) and Drizzle Database (ChatbotXIO/ChatbotX, 878 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Database Schema Changes?
willdady (a GitHub user) maintains it in willdady/platypus, which has 116 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: willdady/platypus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.