Drizzle Safe Migrations

Community

pedronauck

drizzle-safe-migrations

Plan safe Drizzle backfills, enum/check/default changes, constraint tightening, migration ordering, and rollback. Excludes other ORMs, query optimization, and new-schema design.

Overview

Publisher	pedronauck
Repository	`skills`
Skill name	`drizzle-safe-migrations`
Stars	635
Forks	89
Bundled files	2
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by pedronauck on GitHub. Read the source before you install it.

Installation

Install the Drizzle Safe Migrations AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/pedronauck/skills/tree/main/skills/mine/drizzle-safe-migrations
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/pedronauck/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/mine/drizzle-safe-migrations .claude/skills/drizzle-safe-migrations

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Drizzle Safe Migrations in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Drizzle Safe Migrations on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Drizzle Safe Migrations is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Drizzle Safe Migrations

Overview

Use this skill to run database migrations in a way that is auditable, deployment-safe, and consistent with Drizzle's migration model.

Core Rules

Generate schema migrations with the existing project script and package manager; bun run db:generate below is an example, not a required script name.
Never hand-edit generated schema migration files.
Generate data backfills as custom migrations (bun run db:generate -- --custom --name <name>) and edit only that custom SQL file.
Apply data normalization before tightening constraints.
Keep one-off data fixes in migration history, not as hidden runtime logic, unless an emergency hotfix requires temporary mitigation.

Workflow

Classify the change:
- schema-only: only column/table/index/default changes.
- data+schema: old rows must be transformed before new constraints/defaults.
For data+schema, create custom migration first:
- bun run db:generate -- --custom --name <descriptive_name>
- Add idempotent backfill SQL.
Generate schema migration second:
- bun run db:generate
Verify migration ordering in drizzle/meta/_journal.json:
- backfill migration index must be lower than constraint-tightening migration index.
Verify generated SQL and snapshots:
- backfill migration contains only intended data change.
- schema migration contains constraint/default/type changes.
Run the owning migration suite against existing-data and fresh-install cases, plus required project gates. Reuse current evidence; unrelated backend suites are not an additional skill gate.
Record material rollout risks and recovery steps when applicable:
- expected data transformations,
- lock-risk areas,
- rollback strategy.

Backfill Requirements

Use restrictive WHERE clauses.
Prefer idempotent updates (UPDATE ... WHERE status = 'legacy_value').
Do not mix unrelated DDL/DML in the same migration.
Keep SQL explicit and minimal.

Constraint Tightening Pattern

When removing allowed values (enum/check):

Backfill existing rows to valid target value.
Update default to new value.
Tighten check/enum constraint.

For large tables or strict uptime targets, evaluate staged constraint validation supported by the actual database and driver. PostgreSQL NOT VALID / VALIDATE CONSTRAINT applies only to supported constraint kinds.

Anti-Patterns

Hand-editing generated schema migration files.
Tightening constraints before backfilling existing data.
Hiding one-time migration logic in app startup code without migration artifacts.
Running migrations without validating order in the Drizzle journal.

Reference

See references/production-playbook.md for command templates and review checklists.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB
references/production-playbook.md2 KB

Frequently asked questions

What does the Drizzle Safe Migrations AI skill do?

Plan safe Drizzle backfills, enum/check/default changes, constraint tightening, migration ordering, and rollback. Excludes other ORMs, query optimization, and new-schema design.

Why use Drizzle Safe Migrations on TypingMind?

Because you install it once and use it with any model. Drizzle Safe Migrations is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Drizzle Safe Migrations in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/pedronauck/skills/tree/main/skills/mine/drizzle-safe-migrations. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Drizzle Safe Migrations?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Drizzle Safe Migrations?

As many as you like. As long as a model supports skills, you can use Drizzle Safe Migrations with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Drizzle Safe Migrations AI skill free?

It is published on GitHub by pedronauck. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

1password

openclaw

OrganizationPopular

Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.

Apple Reminders

List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.

Clawhub

Search ClawHub for skills when a requested capability is not already available; install, verify, update, uninstall, publish, or sync skills.

Diagnosing Superpowers

obra

CommunityPopular

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Drizzle Safe Migrations

Overview

Core Rules

Workflow

Backfill Requirements

Constraint Tightening Pattern

Anti-Patterns

Reference

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now