Agent skill · data analytics · sickn33
drizzle-migration-conflict
Diagnose, repair, and prevent Drizzle Kit migration conflicts involving generated SQL, snapshots, journals, merge queues, and team workflows.
Why this skill is useful
Provides domain-specific knowledge on handling Drizzle Kit migration conflicts that the AI wouldn't reliably generate on its own.
What it needs
Requires git, python, rg installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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, or run git checkout --ours, git checkout --theirs, git restore, or rm unless the user has confirmed the exact side and files to change. Do not recommend drizzle-kit push as the production solution for migration conflicts; it skips the auditable migration history that teams need. Treat --ignore-conflicts as an exception for a known false positive, not as the normal fix. Preserve schema source code changes unless the user explicitly asks to discard them. Conflict repair normally discards generated migrations and regenerates them from the merged schema. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/drizzle-migration-conflict--86a1e2