supabase-deep

Automate Supabase schema migrations, type generation, and RLS policy testing.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/adiomas/claude-code-adiomas-plugins --skill supabase-deep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase-deep
Source: https://github.com/adiomas/claude-code-adiomas-plugins/tree/main/autonomous-dev/skills/supabase-deep
Command: npx skills add https://github.com/adiomas/claude-code-adiomas-plugins --skill supabase-deep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full workflow automation for Supabase projects, including migrations, type generation, and RLS policy checks, all orchestrated via MCP tools.

Core Features & Use Cases

  • Automated migrations generation and application with safety checks
  • TypeScript types synchronization after schema changes
  • RLS policy testing and logs retrieval for audit
  • Schema snapshot and rollback support

Quick Start

Install and configure Supabase MCP integration in your project. Modify SQL/migrations files or run the /db command to trigger actions. After migrations, run type generation to update TypeScript types and verify with your tests.

Frequently Asked Questions about supabase-deep

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

FAQPage Schema
How do I automate Supabase migrations and TypeScript type generation?

The workflow automates Supabase migrations and TypeScript type generation by using configured MCP tooling to apply schema changes, regenerate types, and run safety checks across development and production branches.

Can I test RLS policies and retrieve logs for audit in Supabase?

Yes, the workflow validates RLS policies and retrieves logs for audit by running integrated verification checks through the configured Supabase MCP tooling after applying schema migrations.

Do I need a configured Supabase MCP tool to run schema migrations?

Yes, you need a configured Supabase MCP tool and a repository with SQL migration files to execute automated schema migrations, generate rollback scripts, and synchronize TypeScript types.

What is the best way to handle rollback and backup before Supabase schema changes?

The best way to handle rollback and backup is to use the workflow's automated pre-migration snapshots and rollback scripts, which verify safety checks before applying schema changes to production branches.

Does Supabase type synchronization work across development and production branches?

Yes, Supabase type synchronization works across development and production branches by automatically regenerating TypeScript types after schema migrations are applied and verified.