How do I install the DB Change skill?

Run npx skillmds@latest add skillist-io/db-change in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the DB Change skill do?

The correct flow for changing the Postgres schema (packages/db, Drizzle): edit schema.ts, generate the migration, migrate. Use when adding/altering tables, columns, enums, indexes, or relations. It is listed under Coding & Dev Tools on SkillMD.

Is DB Change safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with DB Change?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is DB Change free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published DB Change?

skillist-io (@skillist-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

DB Change by skillist-io — Agent Skill

Name: DB Change
Author: skillist-io

File contents

Database schema change

Change requested: $ARGUMENTS

The only correct flow

Edit packages/db/src/schema.ts — the single source of truth (~30 pgTables + pgEnums). Match existing naming, enum reuse, references() relations, and timestamp conventions. Enums shared with the app mirror @skillist/contracts — keep them in sync.
pnpm db:generate — drizzle-kit writes SQL to packages/db/drizzle/NNNN_*.sql and updates meta/_journal.json.
pnpm db:migrate — applies against DATABASE_URL from the root .env.

Rules

🚫 Never hand-edit packages/db/drizzle/ — it's generated and Biome-ignored. Wrong SQL? Fix schema.ts and regenerate.
Prefer additive, backward-compatible changes. For any drop/rename/type-narrow, state the data-loss risk before running db:migrate.
After changing a table, grep apps/api/src for readers/writers and update contracts + route handlers to match. The Worker reads the schema via createWorkerDb(env) over the HYPERDRIVE binding.

Verify

pnpm typecheck (schema and apps/api type errors surface here).
If app code changed: pnpm --filter @skillist/api exec vitest run <path>.

For a non-trivial change spanning tables and call sites, delegate to the db-migrator agent.

Frequently asked questions

DB Change