Run Database Migration

Apply pending Supabase migrations to local or production databases.

412|67|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/pipecat-ai/gradient-bang --skill run-database-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Run Database Migration
Source: https://github.com/pipecat-ai/gradient-bang/tree/main/.claude/skills/migrate
Command: npx skills add https://github.com/pipecat-ai/gradient-bang --skill run-database-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Applies pending database migrations to local or production environments. This skill ensures changes are additive and never resets, truncates, or drops data.

Core Features & Use Cases

  • Identify and apply only pending migrations to keep schemas up to date
  • Preview and review migration SQL before execution, with production safeguards
  • Works across local, dev, and prod environments for consistent database schema

Quick Start

Run the migration skill and specify the target environment to apply any pending migrations after confirming the target database.

Frequently Asked Questions about Run Database Migration

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

FAQPage Schema
How do I apply pending Supabase migrations to a production database safely?

To apply pending Supabase migrations safely, this skill identifies pending changes and previews the SQL before executing, ensuring changes are additive and never reset, truncate, or drop data. It targets local, dev, and prod environments with explicit confirmations.

Can I preview and review migration SQL before execution in production?

Yes, you can review migration SQL before execution. The skill provides a preview of pending changes and enforces production safeguards, requiring explicit confirmation before applying any additive schema updates to your target database.

Do I need the database URL and migration files to run database migrations?

Yes, you need the database URL and migration files to run database migrations. The skill requires knowledge of the target database connection string and your migration files to identify and apply pending schema changes across local, dev, or prod environments.

What is the safest way to apply database migrations without losing data?

The safest way to apply database migrations without losing data is to ensure changes are strictly additive. This skill never resets, truncates, or drops data, applying only pending migrations after you review the SQL and confirm the target environment.

Does this database migration skill work across local, development, and production environments?

Yes, this database migration skill works across local, dev, and prod environments. It applies pending Supabase migrations consistently across different environments, requiring you to specify the target and confirm before executing the reviewed SQL changes.