supabase-migration-hygiene

Name: supabase-migration-hygiene
Availability: InStock
Author: buurguees

Enforces governance and validation for Supabase migrations using the CLI.

1|Updated Dec 30, 2025

Search Tags:#rollback #validation #migration #supabase #drift #hygiene

Ready to run

npx skills add https://github.com/buurguees/av-tech-p-gina-de-inicio --skill supabase-migration-hygiene

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: supabase-migration-hygiene
Source: https://github.com/buurguees/av-tech-p-gina-de-inicio/tree/main/.agents/skills/supabase-migration-hygiene
Command: npx skills add https://github.com/buurguees/av-tech-p-gina-de-inicio --skill supabase-migration-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline the hygiene, validation, and governance of Supabase migrations to prevent drift, duplicate timestamps, and execution errors across environments.

Core Features & Use Cases

Enforces migration naming conventions and unique timestamps.
Detects and guides remediation for drift between local and remote migrations.
Provides a controlled workflow from migration creation to deployment, including rollback planning.

Quick Start

Describe the exact migration change you want to implement and confirm you are ready to run hygiene checks before deployment.

Frequently Asked Questions about supabase-migration-hygiene

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

FAQPage Schema

How do I prevent drift between local and remote Supabase migrations?▼

To prevent Supabase migration drift, use a guided workflow with the Supabase CLI that validates migration naming, detects remote discrepancies, and guides remediation before deployment.

What is the best way to enforce unique timestamps in Supabase migration files?▼

Enforcing unique timestamps in Supabase migration files requires a governance process that blocks duplicate timestamps and temp files during creation, ensuring clean sequential execution across environments.

Why does my Supabase migration deployment fail due to naming or validation errors?▼

Supabase migration deployment fails when hygiene checks are skipped. Validating migration naming conventions and identifying invalid files before execution prevents these errors and ensures a rollback plan.

Can I use the Supabase CLI to plan a rollback before deploying a migration?▼

Yes, you can use the Supabase CLI within a controlled workflow to define a rollback plan before deployment, ensuring safe recovery from drift or execution errors.

When do I need to run Supabase migration hygiene checks?▼

Run Supabase migration hygiene checks when creating, validating, or deploying migrations, especially when recovering from drift or identifying invalid temporary files in your local environment.