Database migrations
Assign a schema or data migration and the engineer plans the change, writes the migration in the repo's toolchain, verifies ordering and rollback risk, updates affected code, and drafts a PR.
Saves you ~1.5 h / run
How it works
- Trigger
- When you start the “Database migration delivery” workflow.
- Job
- Plan, implement, and verify the assigned schema or data migration before human review.
- Outcome
- A tested implementation and pull request draft.
What it installs
Agents 2
-
Database Engineer
Reviews migration history and app call sites, writes safe migrations, verifies ordering and rollback risk, and drafts a PR with validation notes.
-
Database migrations Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Database migrations quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Database migration delivery
Plan, implement, and verify the assigned schema or data migration before human review.
Goals 1
-
Migrations land safely
Keep schema and data changes reversible, ordered, tested, and reviewable. Success looks like: Every migration ships with a reviewed sequence, repository-native migration code, validation evidence, and explicit rollback or production-risk notes.
Skills 2
-
database-migration
Migration planning and execution discipline: expand-contract sequencing, backfills, indexes, rollback safety, data validation, and production-risk review. Adapted from wshobson/agents/database-migration.
-
prisma-migration-assistant
ORM migration guardrails for Prisma-style projects: schema diff review, generated migration inspection, client regeneration, seed compatibility, and drift checks. Adapted from patricio0312rev/skills/prisma-migration-assistant.
Requirements
- Connected repository — Needs a connected repository so the agent can inspect schema history, app code, migration conventions, and tests.
- Runnable database checks — Needs local or CI commands for generating, applying, rolling back, and testing migrations against a disposable database.
Setup guide
How to Automate Database Migrations
A practical guide to using an agent for schema and data migrations with sequencing, verification, rollback notes, and review.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.