ba-db-prisma-migrate

To generate versioned Prisma migrations, the Skill reads your user story and current schema.prisma to identify gaps, then creates a timestamped migration folder under prisma/migrations with a concise summary of the applied changes.

The safest way to apply Prisma schema updates is by validating changes against your project context and architecture first, generating a secure migration path before running commands like npx prisma migrate dev or deploy to prevent destructive data loss.

Yes, the Prisma migration process guides and coordinates running npx prisma generate and database seeding steps alongside migrate dev or deploy, ensuring your Prisma Client stays synchronized with the latest versioned schema changes.

You need to update tsconfig to include prisma and run postinstall prisma generate in monorepo setups whenever schema changes occur, ensuring the Prisma Client is correctly generated and recognized across all workspace packages and IDEs.

Yes, you can identify schema gaps by comparing your existing schema.prisma against the provided ERD or user story, allowing the Skill to calculate necessary structural updates and produce a safe, versioned migration plan before execution.