Results for “migration-planning”

10 skills
More results
github
creating-oracle-to-postgres-master-migration-plan
Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan.
36.2k
openclaw
convex-migration-helper
Plan and execute safe Convex schema and data migrations using the widen-migrate-narrow pattern and the @convex-dev/migrations component.
9.1k · bundle
affaan-m
database-migrations
Provides safe, reversible database schema change patterns for PostgreSQL, MySQL, and common ORMs, with guidance on zero-downtime deployments, rollbacks, and migration tooling.
226k
github
issue-fields-migration
Bulk-migrate repo labels and Project V2 fields into GitHub org-level issue fields (single select, text, number, date).
36.2k · bundle
saranskumar
supabase-schema-designer
Use when designing PostgreSQL tables, enums, relationships, migrations, storage metadata, or tenant-aware schema structures for a Supabase-backed app. Trigger on requests about Supabase schema planning or SQL-first data design.
0
nickgallick
nick-schema-designer
Supabase-first database schema design for Nick's app stack. Generate production-ready Postgres schemas, Supabase SQL migrations, RLS policies, TypeScript types, seed data, role-aware access patterns, and schema checklists from plain English requirements. Use when starting any new project database, designing or reviewing schemas, adding tables, planning migrations, or turning product requirements into Supabase-ready data models. Bias toward product-led schema design, MVP discipline, core-workflow-first modeling, and avoiding premature table/role sprawl.
0 · bundle
herdiansah
database-architect
Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization strategies, migration planning, and performance-first design. Handles both greenfield architectures and re-architecture of existing systems. Use PROACTIVELY for database architecture, technology selection, or data modeling decisions.
23