migrations

Automate versioned SQL schema migrations for Supabase projects.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill migrations-theslashdojo
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: migrations
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/supabase/migrations
Command: npx skills add https://github.com/theslashdojo/dojo --skill migrations-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill requires supabase/cli, and includes scripts (resource) components.

What problem does it solve?

Keeps database schema changes organized, auditable, and repeatable by using versioned migrations, eliminating ad-hoc edits and drift between environments.

Core Features & Use Cases

  • Timestamped SQL migrations that define tables, indexes, policies, and seeds.
  • Tools to diff Studio changes into migrations and push/pull changes to remote databases.
  • Seed data support and environments synchronization for development and production parity.

Quick Start

Create a new migration with the Supabase CLI and push it to the remote database.

Frequently Asked Questions about 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 remote environments?โ–ผ

You can manage Supabase database schema changes by using version-controlled, timestamped SQL migrations. This approach tracks progress in the migrations table, eliminating ad-hoc edits and drift between local development and remote production environments.

What is the best way to version control Supabase RLS policies and seed data?โ–ผ

The best way to version control Supabase RLS policies and seed data is through SQL-first migrations. This method defines tables, indexes, policies, and seeds in timestamped files, ensuring changes remain organized, auditable, and repeatable.

How do I diff Supabase Studio changes into a SQL migration file?โ–ผ

You can diff Supabase Studio changes into a SQL migration file using specific orchestration tools. This process captures visual schema modifications and translates them into timestamped, version-controlled SQL scripts for deployment.

Does this database migration approach require the Supabase CLI?โ–ผ

Yes, this database migration approach requires the Supabase CLI. It relies on the CLI to automate version-controlled schema changes, handle SQL-first migrations, and push or pull changes between local and remote databases.

Why should I use SQL-first migrations for Supabase schema updates?โ–ผ

You should use SQL-first migrations for Supabase schema updates to keep changes organized and repeatable. This method eliminates ad-hoc edits and prevents schema drift by tracking all table, index, and policy modifications in versioned files.