Why is ARCHitect approval mandatory in this skill?

As part of a SAFe multi-agent methodology, architectural approval ensures that schema changes align with the broader system design before any code is generated or applied.

Does this skill support the Prisma ORM?

Yes, it is specifically designed to integrate with 'npx prisma migrate' workflows while adding the necessary SQL layers for RLS and GRANT statements that Prisma does not handle natively.

What makes this migration skill 'security-first'?

It enforces 'Stop-the-Line' conditions that forbid creating tables without Row Level Security (RLS) and requires all security policies to be contained within the same migration file to prevent data exposure.

What roles are covered by the RLS policy templates?

The skill includes pre-defined templates for standard app users, administrative overrides based on user roles, and system-level access for background jobs.

Secure Database Migrations

Name: Secure Database Migrations
Author: bybren-llc

bybybren-llc

•

Database Management

Enforces security-first database migrations with mandatory Row Level Security policies and architectural oversight.

About

The Secure Database Migrations skill provides a production-validated framework for managing database changes within a multi-agent development methodology. It mandates a security-first approach by requiring Row Level Security (RLS) policies to be defined in the same migration file as table creation, ensuring no data is ever exposed. The skill guides developers through a structured workflow—from ARCHitect approval and Prisma schema updates to performance indexing and production validation—to maintain high standards of data integrity and isolation.

Key Features

Mandatory ARCHitect approval workflow for schema changes
Standardized templates for PostgreSQL GRANT statements and security policies
Prevention of insecure patterns like bypassing migration verification
Enforcement of user_id indexing for RLS performance
Automated RLS policy generation for User, Admin, and System roles
19 GitHub stars

Use Cases

Adding new tables to a multi-tenant application requiring strict data isolation
Implementing a standardized database change management process for AI-agent teams
Updating existing Prisma schemas with complex Row Level Security requirements

About

Key Features

Mandatory ARCHitect approval workflow for schema changes
Standardized templates for PostgreSQL GRANT statements and security policies
Prevention of insecure patterns like bypassing migration verification
Enforcement of user_id indexing for RLS performance
Automated RLS policy generation for User, Admin, and System roles
19 GitHub stars

Use Cases

Adding new tables to a multi-tenant application requiring strict data isolation
Implementing a standardized database change management process for AI-agent teams
Updating existing Prisma schemas with complex Row Level Security requirements