supabase-shipper

Audits Supabase deployments for schema, auth, storage, and policy risks.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/blakeox/llm-skills --skill supabase-shipper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase-shipper
Source: https://github.com/blakeox/llm-skills/tree/main/openclaw/skills/supabase-shipper
Command: npx skills add https://github.com/blakeox/llm-skills --skill supabase-shipper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and mitigates potential release issues specific to the Supabase platform, preventing unsafe deployment mistakes that could impact live data or service configurations.

Core Features & Use Cases

  • Audit Migrations and Policies: Review database migrations, RLS policies, auth configs, and storage policies before deployment.
  • Risk Assessment: Detect unsafe schema changes, policy drifts, and potential service-role leakages.
  • Use Case: A developer is preparing a new release containing several schema updates and policy modifications; this Skill audits the changes to flag any risky elements and ensures compliance with safety standards.

Quick Start

Describe the current schema updates and policy changes to the AI to identify any release risks.

Frequently Asked Questions about supabase-shipper

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

FAQPage Schema
How do I audit Supabase database migrations before a release?

To audit Supabase database migrations, you need to review schema changes, RLS policies, and auth configurations. This process detects unsafe modifications and ensures compliance with safety standards before deployment.

What is the best way to prevent unsafe Supabase policy changes?

The best way to prevent unsafe Supabase policy changes is to perform a risk assessment on RLS policies and storage settings. This identifies policy drifts and potential service-role leakages before they impact live releases.

How do I check for service-role leakages in Supabase auth configs?

Checking for service-role leakages in Supabase auth configs requires a detailed deployment plan review. This audit detects potential security vulnerabilities in access policies and ensures error-free service configurations.

Can I review Supabase storage policies for release compliance?

Yes, you can review Supabase storage policies for release compliance by auditing the deployment components. This ensures storage settings meet safety standards across database and auth configurations for secure releases.

What are common risks when deploying Supabase schema updates?

Common risks when deploying Supabase schema updates include unsafe schema changes, policy drifts, and service-role leakages. Auditing deployment plans mitigates these issues and prevents mistakes impacting live data.