supabase-migration

Create and validate Supabase SQL migrations in local files.

43|8|Updated May 21, 2026

Search Tags:#testing #deployment #database #migration #supabase #mcp #sql

Ready to run

npx skills add https://github.com/roedyrustam/vibes-plug --skill supabase-migration-roedyrustam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: supabase-migration
Source: https://github.com/roedyrustam/vibes-plug/tree/main/skills/supabase-migration
Command: npx skills add https://github.com/roedyrustam/vibes-plug --skill supabase-migration-roedyrustam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating and applying database migrations for Supabase, reducing manual scripting and human error.

Core Features & Use Cases

Generate and manage local migration scripts in supabase/migrations with timestamped filenames.
Validate SQL before applying and test migrations locally with npx supabase migration up.
Apply migrations remotely via MCP integration when requested, with safeguards and confirmation steps.
Use Case: When updating a schema for a new feature, create a migration, test locally, and push to remote after verification.

Quick Start

Create a new local migration file in supabase/migrations, test it with the local migration tool, and confirm the migration succeeds.

Frequently Asked Questions about supabase-migration

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

FAQPage Schema

How do I safely create and apply Supabase database migrations?▼

You can validate SQL before applying it by testing migrations locally with the command npx supabase migration up, ensuring correctness before any remote execution.

What's the best way to test Supabase migrations locally before deployment?▼

MCP integration is used to apply validated migrations remotely, requiring environment checks, validation, and a final user confirmation step before executing the deployment.

Do I need to confirm before applying Supabase migrations to a remote database?▼

Yes, a final user confirmation is required before applying migrations remotely via MCP, ensuring safe practices through mandatory environment checks and SQL validation prior to deployment.

Can I list existing Supabase migrations to track what has been applied?▼

Yes, you can list existing migrations to track applied schema changes and manage new local migration scripts using timestamped filenames within the supabase/migrations directory.

Why validate SQL locally before running Supabase database migrations remotely?▼

Validating SQL locally before remote execution reduces manual scripting errors and human mistakes, enforcing safe practices by requiring environment checks and verification before deployment.