prisma-schema

Automate safe Prisma v7 schema changes and migrations for Next.js projects.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/stancodev/obigode --skill prisma-schema-stancodev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-schema
Source: https://github.com/stancodev/obigode/tree/main/.claude/skills/prisma-schema
Command: npx skills add https://github.com/stancodev/obigode --skill prisma-schema-stancodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prisma schema changes and migrations can be risky and data-destroying if not handled carefully. This skill provides a structured, production-grade workflow to identify change types, use create-only migrations, and apply safe SQL edits to preserve data integrity in Prisma v7 with Next.js 16.

Core Features & Use Cases

  • Structured change workflow: guidelines to classify changes (add model, add required field, rename, etc.) and choose the safest migration path.
  • Safe migration practices: use --create-only, review generated SQL, and hand-edit SQL when renaming fields or tables.
  • End-to-end guidance: provides steps from development to production, including validation, data preservation, and rollback considerations.

Quick Start

Identify the change, start with a create-only migration, and follow the safe SQL editing and data-validation steps.

Frequently Asked Questions about prisma-schema

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

FAQPage Schema
How do I safely manage Prisma v7 schema changes and migrations in a Next.js project?

To safely manage Prisma v7 schema changes and migrations in a Next.js project, classify the change type, use --create-only migrations, review generated SQL, and validate data integrity across development and production environments.

What is the safest way to rename a field in a Prisma v7 PostgreSQL database without losing data?

The safest way to rename a field in a Prisma v7 PostgreSQL database without losing data is to generate a --create-only migration, hand-edit the generated SQL, and execute safe SQL edits to preserve data integrity.

Do I need @prisma/adapter-pg and PostgreSQL to use this Prisma schema migration workflow?

Yes, this structured Prisma schema migration workflow requires Prisma v7, the @prisma/adapter-pg package, and an active PostgreSQL connection to operate and validate data integrity correctly.

How does the create-only migration approach work for protecting data integrity during Prisma schema updates?

The create-only migration approach works for protecting data integrity by generating migration SQL without applying it, allowing you to review and hand-edit the SQL before execution to ensure safe schema changes.

What are the limitations of automated Prisma v7 migrations for required fields in Next.js production environments?

Automated Prisma v7 migrations for required fields in Next.js production environments risk data destruction if applied directly, requiring create-only migrations and manual SQL edits to bypass these limitations and preserve data.