Database Migrations taste
# Database Migrations taste - Keep every schema change in a versioned migration file committed next to the code that needs it. Confidence: 0.
- Kind
- Prompt
- Works with
- Any agent
- Source
- prompts.chat: prompts for developers @ dcab86ce9c26
- Path
- items/database-migrations-taste
- Jobs
- Review, Debugging, Testing
- Topics
- Databases
- Tags
- role-prompt
Credit
- Made by
- f
- Original
- https://prompts.chat/prompts?q=Database+Migrations+taste
- License
- CC0-1.0
Listed by Skill Manifest; not made by us.
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
Install factsScanned 2 Nov 2026
- Adds
- A prompt to paste or save as a command
- Runs scripts
- None found
- Uses the network
- None found
- Needs secrets
- None found
- Source revision
- dcab86ce9c26
- Licence
- CC0-1.0
- Last activity
- Unknown
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
- The source's last activity is not known yet
# Database Migrations taste - Keep every schema change in a versioned migration file committed next to the code that needs it. Confidence: 0.95 - Write migrations in plain SQL rather than ORM-generated diffs you have not read. Confidence: 0.80 - Never edit a migration that has already run in a shared environment; add a new one instead. Confidence: 0.95 - Use the expand and contract pattern: add the new column, backfill, switch reads, then drop the old column in a later release. Confidence: 0.90 - Make every migration safe to run while the previous app version is still serving traffic. Confidence: 0.90 - Add new columns as nullable or with a constant default to avoid long table rewrites. Confidence: 0.85 - Create indexes on large Postgres tables with CREATE INDEX CONCURRENTLY outside a transaction. Confidence: 0.90 - Set a short lock_timeout and statement_timeout at the top of each migration. Confidence: 0.85 - Run large backfills as batched background jobs, not inside the migration itself. Confidence: 0.90 - Keep one logical change per migration so failures are easy to read and retry. Confidence: 0.80 …