migrate

Automate Prisma migrations across environments with validation and tenant isolation checks.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/azadmotala/claude-code-team-builder --skill migrate-azadmotala
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/azadmotala/claude-code-team-builder/tree/main/examples/saas-dashboard/.claude/skills/migrate
Command: npx skills add https://github.com/azadmotala/claude-code-team-builder --skill migrate-azadmotala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and safeguards Prisma migrations for TenantFlow, ensuring changes are reviewed and verified before applying to databases.

Core Features & Use Cases

  • Show pending migrations in Prisma projects and summarize changes
  • Review, validate, and approve migrations before deployment
  • Confirm before running migrations on staging or production environments
  • Run migrations and verify success with tenant isolation checks
  • Maintain alignment with the project's prisma/migrations directory and environment configurations

Quick Start

Run the migrate command to apply pending migrations, then review results and confirm before deploying to staging or production.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I safely run Prisma migrations on Railway across staging and production?

You can safely run Prisma migrations on Railway by automating execution across development, staging, and production environments with built-in validation checks and approval prompts before applying changes.

What is the best way to validate pending Prisma migrations before deployment?

The best way to validate pending Prisma migrations is to summarize proposed schema changes, verify alignment with the prisma/migrations directory, and perform tenant isolation checks before deployment.

How do I review and approve database schema changes before applying them to production?

You can review and approve database schema changes by generating a summary of pending migrations, validating changes against environment configurations, and requiring explicit confirmation before production deployment.

Does this migration process support multi-tenant database isolation checks?

Yes, the Prisma migration process supports multi-tenant database isolation by verifying tenant boundaries during post-migration checks to ensure schema changes do not breach tenant separation.

What do I need to set up before running Prisma migrations with TenantFlow?

Before running Prisma migrations with TenantFlow, you need Prisma tooling installed and a configured prisma/migrations directory to validate pending migrations and maintain environment alignment.