supabase-migrations

Create versioned SQL migration files for Supabase database schema changes.

1|Updated Jan 8, 2026

Search Tags:#database #migrations #rls #schema #supabase #sql

Ready to run

npx skills add https://github.com/JaveedIshaq/ai-workflow-orchestrator --skill supabase-migrations-javeedishaq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: supabase-migrations
Source: https://github.com/JaveedIshaq/ai-workflow-orchestrator/tree/main/skills/supabase/migrations
Command: npx skills add https://github.com/JaveedIshaq/ai-workflow-orchestrator --skill supabase-migrations-javeedishaq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating, testing, and deploying database schema changes for Supabase projects, ensuring data integrity and consistency.

Core Features & Use Cases

Migration Generation: Create new, versioned SQL migration files.
Local Testing: Safely reset and test migrations against a local Supabase instance.
Production Deployment: Push schema changes to your live Supabase database.
Use Case: When you need to add a new products table to your e-commerce backend, use this Skill to generate the SQL, test it locally, and then deploy it to production.

Quick Start

Use the supabase-migrations skill to create a new migration file for adding a users table.

Frequently Asked Questions about supabase-migrations

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

FAQPage Schema

How do I manage Supabase database schema changes across local and production environments?▼

Supabase database schema changes are managed through a versioned migration system using specific SQL migration files and Supabase CLI commands. This ensures data integrity and consistency when applying table creation, column alterations, and index management across local and production deployments.

What is the best way to create and test Supabase migrations before deploying to production?▼

The best way to handle Supabase migrations is to generate versioned SQL migration files, safely reset and test them against a local Supabase instance, and then push the validated schema changes to your live production database.

Can I use Supabase migrations to manage Row Level Security policies?▼

Yes, Supabase migrations support Row Level Security (RLS) policy implementation. The versioned migration system applies RLS policies alongside table creation, column alterations, and index management through formatted SQL files.

Do I need the Supabase CLI to apply database migrations?▼

Yes, the Supabase CLI is required for local and production deployments. The migration system relies on specific Supabase CLI commands to apply versioned SQL files for schema changes like table creation and index management.

Why use a versioned migration system for Supabase schema changes?▼

A versioned migration system streamlines creating, testing, and deploying Supabase schema changes, ensuring data integrity and consistency. It tracks table alterations, index management, and RLS policies through formatted SQL files for safe local testing before production deployment.

How do I generate a new SQL migration file for a Supabase database table?▼

You generate a new SQL migration file by creating a versioned file formatted for the Supabase migration system. This file defines the schema changes, such as adding a new products table, which can then be tested locally before production deployment.