prisma-change

Automate Prisma schema changes with migrations, client regeneration, and service updates.

30|3|Updated Mar 8, 2020
One-click install
npx skills add https://github.com/uxname/liteend --skill prisma-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-change
Source: https://github.com/uxname/liteend/tree/main/.agents/skills/prisma-change
Command: npx skills add https://github.com/uxname/liteend --skill prisma-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The user wants to modify the database schema in the project. This is a multi-step workflow where skipping any step causes runtime errors.

Core Features & Use Cases

  • Edit prisma/schema.prisma to apply model, enum, and field changes while adhering to project conventions.
  • Create migrations, regenerate Prisma client, and update affected services to keep code in sync.
  • Ensure compatibility with GraphQL types by coordinating with the /add-graphql-type workflow for type updates when schemas change.

Quick Start

Edit prisma/schema.prisma, then follow the four-step workflow to create migrations, regenerate the client, and update affected services.

Frequently Asked Questions about prisma-change

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

FAQPage Schema
How do I automate Prisma schema changes to prevent runtime errors in NestJS?

Automating Prisma schema changes prevents runtime errors by executing a multi-step workflow that edits schema.prisma, creates migrations, regenerates the Prisma client, and updates affected NestJS services.

What is the correct workflow for updating Prisma database schemas with PostgreSQL?

The correct workflow for updating Prisma schemas involves editing schema.prisma, creating database migrations, regenerating the Prisma client, and updating services to keep code in sync with PostgreSQL changes.

Does Prisma schema migration automatically enforce database conventions like createdAt and updatedAt?

Yes, the schema migration process enforces database conventions like id, createdAt, and updatedAt fields when applying model, enum, and field changes to schema.prisma to maintain data consistency.

How do I keep GraphQL types in sync when modifying a Prisma schema?

To keep GraphQL types in sync when modifying a Prisma schema, the workflow coordinates with the add-graphql-type workflow to ensure type compatibility and update definitions when schemas change.

Can I skip Prisma client regeneration if I only add a new field to an existing model?

No, skipping Prisma client regeneration when adding a new field causes runtime errors because the generated client lacks the updated type definitions needed by affected NestJS services.