db-migrations

npx skills add lobehub/lobehub --skill db-migrations --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Database Migrations Guide ## Choose the rollout strategy Classify every database change into one of these three rollout paths before generating or editing a migration. ### 1. Regular Drizzle migration Use the normal Drizzle workflow for schema changes that are safe to execute during deployment, such as creating a small table or adding a nullable column: 1. Update the Drizzle schema. 2. Run `bun run db:generate`. 3. Review and harden the generated artifacts using the steps below. Before listing a manual migration command as a release step, inspect the target repository's build and deployment scripts. If its deployment pipeline already applies migrations automatically, do not require a redundant manual run. ### 2. Online index creation Creating an index normally can block writes and queries on a large or frequently accessed table, and a long-running statement can also stall the deployment. In that case: 1. Before deploying the application, execute the index creation manually in the target database's SQL editor using `CONCURRENTLY`: ```sql CREATE INDEX CONCURRENTLY IF NOT EXISTS "table_column_idx" ON "table" USING btree ("column"); ``` 2. Keep an idempotent, non-`CONCURRENTLY` versi

rm packages/database/migrations/0110_add_verify_tables_and_ai_infra_id.sql
rm packages/database/migrations/meta/0110_snapshot.json
packages/database/migrations/meta/_journal.json
bun run db:generate
rm packages/database/migrations/011{0,1,2}_*.sql
rm packages/database/migrations/meta/011{0,1,2}_snapshot.json
Fix the dev DB to match the new schema (simplest SQL wins)
set -a && source .env && set +a && bun -e '
import pg from "pg";
const client = new pg.Client({ connectionString: process.env.DATABASE_URL });