infra-ops

Governs Supabase deployments via managed migrations, policies, and secrets.

Updated Nov 9, 2025
One-click install
npx skills add https://github.com/canyouseeus/thelostandunfounds --skill infra-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infra-ops
Source: https://github.com/canyouseeus/thelostandunfounds/tree/main/.agent/skills/infra-ops
Command: npx skills add https://github.com/canyouseeus/thelostandunfounds --skill infra-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Infrastructure governance for database migrations, access controls, and environment variable management to ensure deployment integrity and security across environments.

Core Features & Use Cases

  • Enforce idempotent migrations with safe checks.
  • Apply default-deny RLS policies and secret handling guidance.
  • Support deployment verification and environment synchronization.

Quick Start

Follow the infra-ops guidelines when applying Supabase migrations, RLS policies, and environment variable configurations in deployments.

Frequently Asked Questions about infra-ops

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

FAQPage Schema
How do I automate Supabase migrations to ensure they are safe and idempotent?

Automating Supabase migrations requires enforcing idempotent migration checks to prevent schema drift. This approach ensures safe, consistent database schema changes across development, staging, and production deployments without manual intervention.

What is a default-deny RLS policy and how does it secure Supabase deployments?

A default-deny RLS policy blocks all table access by default until explicit permissions are granted. Applying default-deny RLS policies in Supabase enforces strict access control and ensures deployment integrity across all environments.

How do I manage environment variables securely across staging and production deployments?

Secure environment variable management involves applying server-side patterns and tooling to handle secrets consistently. This practice ensures environment synchronization and protects sensitive configuration data across development, staging, and production deployments.

Can I verify database schema changes and access controls before applying them to production?

Verifying schema changes and access controls before production is supported through deployment verification. This process checks Supabase migrations and RLS policies to ensure environment synchronization and consistent infrastructure governance before release.

Why do my database schema changes cause inconsistencies between development and staging environments?

Schema changes cause inconsistencies when infrastructure governance lacks enforced idempotent migrations. Applying safe checks and environment synchronization patterns ensures consistent database schema changes and access controls across all deployment environments.

What's the best way to handle infrastructure governance for database migrations and secrets?

Handling infrastructure governance for migrations and secrets requires automating schema changes, applying default-deny RLS policies, and enforcing secure environment variable practices. This approach ensures deployment integrity and security across all environments.