db-change

Orchestrate Prisma and Supabase schema migrations with synchronized mock updates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hemant0510/rwa --skill db-change-hemant0510
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-change
Source: https://github.com/hemant0510/rwa/tree/main/.claude/Skills/db-change
Command: npx skills add https://github.com/hemant0510/rwa --skill db-change-hemant0510

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely coordinate and apply Prisma + Supabase schema changes while preserving mocks and avoiding risky pooler-based DDL operations.

Core Features & Use Cases

  • Direct schema migration workflow: follow a defined sequence to implement and verify schema changes with Prisma.
  • Mock synchronization: automatically prepare and refresh model mocks to reflect new or updated schemas.
  • Pooler avoidance guidance: explicit steps to bypass pooler port 6543 for reliable DDL.

Quick Start

Invoke db-change whenever you edit the Prisma schema or add a migration to apply changes directly against the database while refreshing mocks.

Frequently Asked Questions about db-change

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

FAQPage Schema
How do I run safe Prisma migrations on Supabase without breaking the pooler?

This Skill orchestrates safe Prisma migrations on Supabase by bypassing the pooler on port 6543 for direct database connections, ensuring reliable DDL operations without disrupting pooled traffic.

Why do my Supabase schema migrations fail when using a Prisma pooler connection?

Supabase schema migrations fail over the pooler because DDL operations are risky through port 6543. You need a direct database connection to apply schema changes reliably and avoid pooler conflicts during migration execution.

What is the correct sequence to update Prisma mocks after a schema change?

The correct sequence to update Prisma mocks involves regenerating the Prisma client and refreshing model mocks immediately after applying schema changes. This synchronization must occur before seeding to ensure mocks match the updated schema.

Can I use Prisma migrations to directly alter my Supabase production database schema?

Yes, you can use Prisma migrations to directly alter your Supabase production database schema. The process requires explicit steps to ensure a direct connection, applying changes safely across development and production environments.

How do I synchronize Prisma client mocks after adding a new Supabase migration?

To synchronize Prisma client mocks after adding a Supabase migration, you must follow a defined sequence to regenerate the client and refresh mocks. This ensures your mock data accurately reflects the new schema before any seeding occurs.