drizzle-migration-conflict

Drizzle Migration Conflict

Use this skill to help a user diagnose, repair, and prevent Drizzle Kit migration conflicts in a multi-developer repository. Drizzle migrations encode both SQL and migration snapshots, so the safe answer depends on the current migration directory shape, the Drizzle Kit version, and the git state.

When to Use This Skill

• Use when Drizzle migration files, _journal.json, or snapshot.json conflict after a pull, merge, rebase, or PR update.
• Use when drizzle-kit check reports non-commutative migrations or migration folder conflicts.
• Use when a team wants a safe repair flow for generated Drizzle migrations after schema changes converge.
• Use when designing CI or merge-queue policy to prevent repeated Drizzle migration conflicts.

Safety rules

• Start in read-only diagnosis mode unless the user explicitly asks to fix files.
• Do not run drizzle-kit migrate, drizzle-kit push, database seed scripts, or any command that

connects to a live database unless the user explicitly requests it and the target is clear.

• Treat drizzle-kit check, project typechecks, and tests as command execution that may load project

config, environment variables, or scripts. Inspect scripts/config first, and require an explicit non-production or disposable target before any DB-backed validation.

• Do not delete migration files, rewrite `_journal.json