Design and validate database schema changes with up/down migration scripts.
npx skills add https://github.com/asalhamed/dev-agents --skill db-migration-asalhamed
Please help me install this Agent Skill. Skill: db-migration Source: https://github.com/asalhamed/dev-agents/tree/main/db-migration Command: npx skills add https://github.com/asalhamed/dev-agents --skill db-migration-asalhamed
Design and validate database schema changes, write safe migration scripts, and ensure backward compatibility with zero-downtime rollbacks.
Initialize a new migration after the architect defines the schema change in ADR and apply it using the project’s zero-downtime workflow.
High-intent search queries and answers about installing and using this skill.
Plan zero-downtime database schema migrations by applying expand-contract strategies, writing idempotent up/down scripts, and validating backward compatibility before deployment. This ensures backward compatibility by separating schema changes into non-breaking expand phases followed by contract phases.
An expand-contract migration strategy is a pattern for evolving database schemas without downtime by expanding the schema with new columns or tables, deploying compatible code, and then contracting the old structure. It ensures backward compatibility throughout the deployment cycle.
Write idempotent database migration scripts by ensuring up and down migration scripts can execute repeatedly without errors, and document rollback procedures for each change. This guarantees safe re-runs and reliable recovery if a deployment fails.
Handle data backfills during schema evolution by scripting data migrations alongside schema changes and validating them through an ADR-driven workflow. This coordinates architects, backend developers, and DBAs to ensure data integrity during zero-downtime deployments.
Yes, this database migration approach applies across multi-technology stacks by enforcing standard up/down migration scripts and rollback procedures. It coordinates ADR-driven schema changes regardless of the specific database platform used.
You should not use an expand-contract database migration when a schema change requires immediate deletion or renaming that breaks backward compatibility, as this pattern relies on transitional compatibility. Complex deletions require careful coordination to avoid breaking active deployments.
v4lheruDesign database schemas with normalization, indexing, and migration patterns.
drgaciwExecute database schema and data migrations across Sequelize, TypeORM, and Prisma.
sunholo-dataAutomates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.
a53aliGuide database schema migrations with expand/contract patterns and rollback strategies.
