veta-supabase-production

Enforce authorization guardrails for config, SQL, and migration actions on production Supabase.

1|Updated Nov 26, 2025

Search Tags:#database migrations #supabase #production safety #config push #sql guardrails #environment protection

Ready to run

npx skills add https://github.com/marcogonzalo/studio-manager --skill veta-supabase-production

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: veta-supabase-production
Source: https://github.com/marcogonzalo/studio-manager/tree/main/.agents/skills/veta-supabase-production
Command: npx skills add https://github.com/marcogonzalo/studio-manager --skill veta-supabase-production

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents accidental destructive or environment-breaking operations against the hosted production Supabase project by enforcing explicit safety guardrails.

Core Features & Use Cases

Production safety hard rules: Blocks risky actions like supabase config push to production and any non-authorized SQL/migration/DB push targeting the remote.
Authorization-first workflow: Requires the user to explicitly request and confirm intent before any potentially harmful production action.
Safe diagnostics guidance: Allows safer paths (e.g., dashboard-driven inspection or read-only diagnosis) while still keeping production-impacting actions under confirmation.

Quick Start

Ask your AI assistant to use veta-supabase-production before attempting any config, SQL execution, db push, or migration against the hosted Supabase project.

Frequently Asked Questions about veta-supabase-production

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

FAQPage Schema

How do I prevent accidental database migrations to my production Supabase instance?▼

To block unsafe Supabase config push to production, you need an authorization-first workflow that disallows production config pushes entirely. This safety mechanism intercepts CLI operations and requires explicit user confirmation before executing any remote config changes.

Can I run SQL queries against a hosted production Supabase project without risking data loss?▼

You can use SQL guardrails for Supabase production safety to block non-authorized writes and prevent environment-breaking operations. These guardrails intercept MCP tool usage and CLI workflows, requiring explicit user confirmation before any potentially harmful production action occurs.

What is the best way to enforce environment protection for remote Supabase databases?▼

The best way to enforce environment protection for remote Supabase databases is to implement hard production safety rules that disallow config pushes and block automatic migrations. This ensures safe diagnostics guidance while keeping production-impacting actions under strict confirmation.

Why does my Supabase CLI workflow need explicit authorization for production actions?▼

Your Supabase CLI workflow needs explicit authorization for production actions to prevent accidental destructive or environment-breaking operations against the hosted project. Requiring explicit intent confirmation ensures that risky SQL, migrations, and database pushes cannot execute automatically without user approval.

NagyVikt

supabase-cli

Manage Supabase CLI workflows for local environments, migrations, and TypeScript types.

Community

Intermediate

YSheldon

database

Execute and manage PostgreSQL databases with environment isolation and read-only production access.

Community

Intermediate

sunholo-data

AILANG Release Manager

Automates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.

Official

Intermediate