Automate multi-tenant database migrations with tenant isolation and rollbacks.
npx skills add https://github.com/Valynt/ValueOS --skill db-migration-valynt
Please help me install this Agent Skill. Skill: db-migration Source: https://github.com/Valynt/ValueOS/tree/main/.windsurf/skills/db-migration Command: npx skills add https://github.com/Valynt/ValueOS --skill db-migration-valynt
Migrations for multi-tenant databases are error-prone without standardized templates, tenant-scoped access controls, and safe rollback mechanisms. This Skill provides a structured workflow and templates to enforce consistent migration patterns, RLS policies, and type updates across infra/supabase migrations.
Create a new migration file using the timestamped format and provide a matching rollback using the templates in references/migration-template.sql and references/rollback-template.sql
High-intent search queries and answers about installing and using this skill.
Automate multi-tenant database migrations by using timestamped migration files, matching rollback scaffolding, and explicit organization_id constraints. This enforces tenant isolation and provides auditable rollback planning across schema changes and access policies.
Enforce tenant isolation in PostgreSQL migrations by applying Row Level Security (RLS) policies and explicit organization_id constraints. This ensures access controls remain scoped to individual tenants during schema and data updates.
The best way to manage Supabase migrations across tenants is standardizing the workflow with timestamped file naming and rollback templates. This enforces consistent migration patterns, RLS policies, and TypeScript type updates.
Yes, you can update TypeScript types when applying database schema changes. The migration workflow guides explicit type updates and integration steps for related backend services, ensuring type safety after schema modifications.
You need a rollback file for your database migration because the workflow enforces safe rollback mechanisms by requiring matching rollback scaffolding. This provides auditable recovery options for schema changes, access policy updates, and data migrations.
Yes, the migration workflow requires lint checks and validation steps. It enforces workflow rules by validating timestamped migration files, rollback scaffolding, and explicit dependency or type updates before applying changes.
ValyntAutomate creation, auditing, and enforcement of PostgreSQL row-level security policies.
monobaselabsGenerate and apply Drizzle ORM migrations for Bun-based services.
linenoizeGenerate rollback-aware database migration files and validate schema changes.
AHMADJAN-NewEnforce Nazim database migration patterns for multi-tenancy and secure SQL.
