What problem does it solve? Editing prisma/schema.prisma and creating migration files safely is error-prone: prisma migrate dev offers to reset the local database, migration ordering breaks on fresh applies, and removed CLI flags cause silent failures. This Skill provides ready-made commands to generate, verify, and apply migrations without touching the local or production database. ## Core Features & Use Cases - Shadow schema check: Runs npm run check:schema against a shadow database to verify migrations match the schema before merge. - One-off container workflow: Spins up a disposable postgres:16-alpine Docker container to apply the migration chain and diff it against the schema. - Migration file generation: Writes migration.sql via prisma migrate diff --script instead of prisma migrate dev, protecting local data. - Rename recovery: Fixes renamed migrations with prisma migrate resolve --applied when apply fails on existing relations. - Use Case: After editing prisma/schema.prisma to add a bookings table, run the container chain to generate the migration file, verify it with the shadow check, and apply it locally with prisma migrate deploy. ## Quick Start Ask the assistant to create a Prisma migration for the current schema changes using the one-off Docker container workflow and verify it with the schema check.
