rls-rollout

Coordinate phased Postgres RLS rollouts with migration plans, runbooks, and tests.

3|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/webdevcom01-cell/agent-studio --skill rls-rollout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rls-rollout
Source: https://github.com/webdevcom01-cell/agent-studio/tree/main/skills/rls-rollout
Command: npx skills add https://github.com/webdevcom01-cell/agent-studio --skill rls-rollout

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Audits, plans, and orchestrates a phased Postgres Row-Level Security (RLS) rollout for the agent-studio multi-tenant database, enabling safe, auditable deployments without automatic migrations.

Core Features & Use Cases

  • Orchestrates end-to-end RLS rollout workflows across a complex 61-model schema, including TENANT_DIRECT, TENANT_INDIRECT, USER_OWNED, GLOBAL, and AMBIGUOUS classifications.
  • Generates migration drafts, runbooks, and cross-tenant test suites, all gated with explicit human approval steps.
  • Provides templates, step-based scripts, and verification guidance to ensure safe production cutovers and robust rollback options.

Quick Start

Start by running the preflight audit, then inventory, plan, and draft steps to begin the RLS rollout.

Frequently Asked Questions about rls-rollout

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

FAQPage Schema
How do I safely orchestrate a phased Postgres RLS rollout for a multi-tenant schema?

To safely orchestrate a phased Postgres RLS rollout, you can run a preflight audit, inventory your models, generate migration drafts, and create runbooks with explicit human approval gates to prevent automatic migrations.

How does row-level security handle indirect tenant relationships in Prisma models?

Row-level security handles indirect tenant relationships by classifying models into categories like TENANT_INDIRECT and TENANT_DIRECT, ensuring cross-tenant test suites verify data isolation across complex schema dependencies.

What is the best way to apply RLS migrations without causing production downtime?

The best way to apply RLS migrations without downtime is using step-based scripts and verification guidance that enforce human gates, ensuring safe production cutovers and robust rollback options.

Does this RLS rollout process auto-apply database migrations to Postgres?

No, this RLS rollout process never auto-applies migrations. It generates migration drafts and runbooks that require explicit human approval steps before any changes are executed against the database.

Can I use this approach for a complex schema with ambiguous data ownership?

Yes, you can use this approach for complex schemas with ambiguous data ownership because it classifies models into AMBIGUOUS, USER_OWNED, and GLOBAL categories to generate tailored policy templates and tests.

Why do I need human approval gates for row-level security policy changes?

You need human approval gates for row-level security policy changes to maintain auditable deployments, verify cross-tenant test results, and prevent unintended data exposure during production cutovers.