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.

What it installs

Agents 1

  • Database Engineer

    Reviews migration history and app call sites, writes safe migrations, verifies ordering and rollback risk, and drafts a PR with validation notes.

Goals 1

  • Migrations land safely

    Keep schema and data changes reversible, ordered, tested, and reviewable.

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

What this template expects to do its job. Task Machine does not verify these — you decide whether your setup is ready.

  • 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.

Get started

Install Database migrations and run it with approvals.

Join the waitlist and we will send early access when the first private beta spots open.

Private beta. We invite teams in batches and never share your email.