prisma-migrate-dev

Name: prisma-migrate-dev
Availability: InStock
Author: Hyperjump

Generate and apply Prisma schema migrations with prisma migrate dev.

1|1|Updated Jan 5, 2026

Search Tags:#database #migrations #migration #prisma #schema-prisma #db:migrate:dev

Ready to run

npx skills add https://github.com/hyperjumptech/mediapulse --skill prisma-migrate-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prisma-migrate-dev
Source: https://github.com/hyperjumptech/mediapulse/tree/main/.cursor/skills/prisma-migrate-dev
Command: npx skills add https://github.com/hyperjumptech/mediapulse --skill prisma-migrate-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prisma migrations can be error-prone when schema.prisma changes; this skill guides users to generate and apply migrations using Prisma migrate dev, ensuring migrations are generated by Prisma and committed with the change.

Core Features & Use Cases

Automatically generate and apply Prisma migrations via Prisma migrate dev as part of the project workflows.
Enforce safety by avoiding manual edits to generated migration files and by committing new migration folders and the migration.sql.
Use cases include adding models or fields, evolving relations, and deploying schema changes across the Hermes orchestration-database and Mediapulse database packages.

Quick Start

Run the Prisma migrate dev workflow from the repository root after editing schema.prisma to generate and apply migrations.

Frequently Asked Questions about prisma-migrate-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Prisma migrations when schema.prisma changes?▼

Automate Prisma migrations by running the prisma migrate dev workflow from the repository root after editing schema.prisma. This coordinates generating, validating, and applying migrations across the Hermes orchestration-database and Mediapulse database packages.

Why does prisma migrate dev require committing the generated migration folders?▼

Committing generated migration folders and migration.sql ensures migrations are safely tracked and generated by Prisma. This enforces avoiding manual edits to migrated SQL, keeping schema changes consistent with the project workflow.

Can I manually edit Prisma migration SQL files after they are generated?▼

Manual edits to migrated SQL are prohibited. Prisma migrations must be generated by Prisma migrate dev to ensure safety, and the generated migration folders and migration.sql must be committed directly without modification.

What's the best way to add models or fields to a Prisma schema safely?▼

The best way to add models or evolve relations is to edit schema.prisma and run the prisma migrate dev workflow. This generates and applies migrations automatically, enforcing safe schema changes across the Hermes and Mediapulse database packages.

When do I need to run prisma migrate dev for my database packages?▼

You need to run prisma migrate dev whenever schema.prisma changes in the Hermes orchestration-database or Mediapulse database packages. It coordinates validating and applying migrations to keep your database schema synchronized.