db-migration-generator
Generator สำหรับสร้าง database migration files พร้อม up/down scripts, validation และ rollback safety
Generator สำหรับสร้าง database migration files พร้อม up/down scripts, validation และ rollback safety
Set up SQLite database with Prisma ORM and Better Auth for user authentication. Use when the user asks for a full backend, database and auth, or needs needs user accounts, login/signup, or persistent data storage.
Create and manage database migrations for schema changes, ensuring zero-downtime deployments and data integrity. Use this skill when creating migration files, modifying database schemas, adding or altering tables/columns/indexes, or working with migration tools like Alembic, Flyway, Liquibase, or framework-specific migration systems (Django migrations, Rails migrations, Prisma migrations). Apply this skill when implementing reversible migrations with up/down methods, handling data migrations separately from schema changes, creating indexes on large tables, or planning backwards-compatible schema changes for high-availability systems. This skill ensures migrations are version-controlled, focused, safe to rollback, and compatible with CI/CD pipelines and zero-downtime deployment strategies.
Handle version migrations, database schema changes, and breaking changes. Use when upgrading framework versions or migrating data.
Creates Supabase RPCs with migrations, RLS, repository integration, and pgTAP tests. Use when asked to create an RPC, add a database function, or implement a new backend endpoint.
Handle version migrations, database schema changes, and breaking changes. Use when upgrading framework versions or migrating data.
Updates schema documentation to synchronize with live database state after migrations or schema changes, preventing documentation drift by querying actual table structures, column definitions, and constraints to update VERIFIED_TABLE_NAMES.md and schema reference files. Use this skill when: (1) After applying database migrations to sync docs with new schema, (2) After pulling migrations from git to update local documentation, (3) When documentation seems outdated or incorrect, (4) Before writing SQL to verify current table names and structure, or (5) To ensure single source of truth between database and documentation
Zero-downtime Elixir/Phoenix database migrations and rollback strategies
Squash database table migration versions in server/src/database.ts. Consolidates multiple migrations into a single initial migration while preserving the final schema.
How to safely create, apply, and verify database migrations using Alembic.
Resets staging database with full schema drop. Use for schema changes or migrations. SINGLE SOURCE OF TRUTH for staging database reset automation.
Configure connection pool sizing for optimal performance. Use when configuring DATABASE_URL or deploying to production.
Create or modify Doctrine entities. Use for database models.
Explain how this repo (and others) reason about defining migrations directly on models, keeping the commands aligned after changes.
Set up and configure DuckDB databases. Use when user needs to create databases, configure settings, or initialize DuckDB projects.
Manage checkpoints for rollback capability. Use when creating save points, rolling back changes, managing recovery points, or restoring previous states.
Chuẩn hoá cách đọc/viết DB model Supabase (migrations + TS types + services) trong repo này.
Supabase 프로젝트 초기 설정. 테이블 생성, RLS 정책, 환경변수 설정, 타입 생성. "Supabase 설정", "DB 셋업" 요청 시 사용.
Run mjr.wtf locally using Docker Compose (SQLite), including migrations, logs, and teardown.
Apply the Agent OS standard for backend migrations.
This skill should be used when working with database migrations in SQLModel-based projects. Trigger when user asks to create migrations for new/modified models, generate database schema changes, or apply migrations. Enforces SQLModel as single source of truth and automatic migration generation only.
A skill for managing database migrations with Alembic. Use this for tasks involving Alembic initialization, configuration, creating new migration scripts (both autogenerated and manual), defining upgrade and downgrade logic, handling data migrations, testing migrations, performing rollbacks, and following production deployment best practices for database changes.
USE IMMEDIATELY when user reports TODO accessibility issues or session migration detected. Restores TODO context using policy-guided recovery.