Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From database-engineering
Evolve schemas without downtime: expand/contract (add -> backfill in batches -> switch -> drop) across separate deploys, lock-aware DDL (create indexes CONCURRENTLY, nullable-add-then-validate), reversibility, and ordered versioned migrations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/database-engineering:safe-schema-migrationsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Add new (safely) -> **backfill in batches** -> dual-write/switch reads -> drop old. Across **separate deploys**. A rename = add-copy-switch-drop, not `ALTER RENAME` mid-traffic.
Add new (safely) -> backfill in batches -> dual-write/switch reads -> drop old. Across separate deploys. A rename = add-copy-switch-drop, not ALTER RENAME mid-traffic.
Volatile-default add, type change, or SET NOT NULL can lock the table. Use: nullable add + batched backfill + ADD CONSTRAINT ... NOT VALID then VALIDATE; create indexes CONCURRENTLY.
Every migration has a down path / tested rollback. Versioned, ordered, never edit a shipped migration. Sequence with devops-cicd/release-engineer.
npx claudepluginhub mcorbett51090/ravenclaude --plugin database-engineeringGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.