db-migrations

Generate and manage Drizzle migration files for database schema changes.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Nick777-Pixel/mychat7 --skill db-migrations-nick777-pixel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-migrations
Source: https://github.com/Nick777-Pixel/mychat7/tree/main/.agents/skills/db-migrations
Command: npx skills add https://github.com/Nick777-Pixel/mychat7 --skill db-migrations-nick777-pixel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when generating or regenerating Drizzle migration files, changing database schema tables or columns, resolving migration sequence conflicts after rebase, reviewing migration SQL for idempotent patterns, or renaming migration files.

Core Features & Use Cases

  • Generate and regenerate Drizzle migration files
  • Review migration SQL for idempotent patterns
  • Resolve migration sequence conflicts after rebase and rename migration files

Quick Start

Run the migration generator to create and apply the initial Drizzle migrations for your project.

Frequently Asked Questions about db-migrations

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

FAQPage Schema
How do I generate idempotent Drizzle migration files for schema changes?

To generate idempotent Drizzle migration files, automate the creation and management of database schema changes by applying SQL patterns that safely re-run without errors. This approach updates journal metadata and enforces safe schema evolution.

What is the best way to resolve Drizzle migration sequence conflicts after a rebase?

Resolving Drizzle migration sequence conflicts after a rebase involves renaming migration files and correcting the journal metadata to restore a valid linear sequence. This ensures the database schema evolution proceeds without sequence errors.

How do I review Drizzle migration SQL for idempotent patterns?

Reviewing Drizzle migration SQL for idempotent patterns means checking that each schema change safely re-executes without duplicating tables or columns. This ensures migration files remain safe to apply across different database environments.

Can I use this to regenerate Drizzle migrations after renaming database schema tables?

Yes, you can regenerate Drizzle migrations after renaming database schema tables or columns. The tooling automates the generation of new migration files, updates the journal metadata, and guides developers through best practices for schema evolution.

When do I need to update Drizzle migration journal metadata?

You need to update Drizzle migration journal metadata whenever you generate, regenerate, or rename migration files to resolve sequence conflicts. This maintains a consistent record of applied database schema changes and ensures proper migration execution order.