migration

Validate Prisma schema changes and generate migration risk reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill migration-reeinharddd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration
Source: https://github.com/reeinharddd/impulsa-monorepo/tree/main/.github/skills/migration
Command: npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill migration-reeinharddd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill validates database schema changes made with Prisma, ensuring they are safe and do not lead to data loss or critical failures.

Core Features & Use Cases

  • Schema Validation: Analyzes proposed changes to prisma/schema.prisma for potential risks.
  • Migration Reporting: Generates reports detailing the risk level of schema modifications.
  • Use Case: When a developer modifies schema.prisma to add a new required field, this Skill will automatically flag it as a medium-risk change and ensure a default value is provided before a migration is generated.

Quick Start

Use the migration skill to validate the latest changes to the prisma schema.

Frequently Asked Questions about migration

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

FAQPage Schema
How do I validate Prisma schema changes before running a database migration?▼

To validate Prisma schema changes, provide the schema diff, existing data, and migration history. The analysis flags risky modifications, such as adding required fields without defaults, ensuring database migration safety.

What happens if I add a new required field to my Prisma schema without a default value?▼

Adding a required field without a default value is flagged as a medium-risk schema modification. The validation process ensures data integrity by requiring a default value before the database migration is generated.

How do I generate a database migration report for Prisma schema modifications?▼

Generating a database migration report involves analyzing your modified schema.prisma file. The report details the risk level of schema modifications to ensure safe database changes and prevent data loss.

Why do I need to provide migration history and existing data to validate a schema diff?▼

Providing migration history and existing data is required for comprehensive schema validation. This context allows the analysis to accurately assess potential data loss risks and ensure safe database schema changes.

Can I check if a database schema change will cause data loss before applying it?▼

Yes, you can check for potential data loss by validating the Prisma schema changes. The analysis automatically flags unsafe modifications and generates a risk report to ensure safe database schema changes.