How do I install the Database Migrations skill?

Run npx skillmds@latest add kilo-org/database-migrations 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.

Is Database Migrations 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 Database Migrations?

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 Database Migrations free to use?

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

Who published Database Migrations?

Kilo-Org (@kilo-org) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Database Migrations by kilo-org — Agent Skill

Name: Database Migrations
Author: Kilo-Org

Database Migrations

Create, review, apply, squash, or validate shared PostgreSQL migrations in this monorepo. Use when changing `packages/db/src/schema.ts`, generating Drizzle migrations, adding backfills, or checking migration bootstrap behavior.

Kilo-Org 0b39b80 1.7 KB Updated Sep 17, 2026

File contents

Shared PostgreSQL migrations

This skill covers shared PostgreSQL migrations only. It does not govern Durable Object SQLite or Wrangler migrations. Read packages/db/AGENTS.md first; it is canonical for shared PostgreSQL and Drizzle invariants. Use the git-rebase skill for migration conflicts during a rebase.

Workflow

Read packages/db/AGENTS.md and inspect relevant schema and migration files.
Change packages/db/src/schema.ts first.
Generate artifacts with pnpm drizzle generate.
Inspect generated SQL.
Review generated DDL for destructive operations and data loss. Prefer additive or staged schema changes. If generated DDL is unsafe, wrong, or too broad, correct the schema and regenerate. Do not hand-edit generated DDL, snapshots, or journal entries.
Append only intentional UPDATE or INSERT data backfills after generated DDL, separated with --> statement-breakpoint.
Apply migrations with pnpm drizzle migrate or run pnpm drizzle:verify-bootstrap when relevant.
Run pnpm format and targeted schema or migration checks.
Prefer one generated migration per unshipped feature branch. To squash migrations before shipping, remove the branch-local migration SQL, snapshots, and journal entries, then regenerate once from the current schema. Re-append intentional backfills afterward.

Keep generated artifacts generated. packages/db/AGENTS.md also covers shared-schema PII requirements and DB-backed timestamp serialization.

Frequently asked questions