mcpField
D
drizzle-orm

drizzle-orm

github.com/liaoannData & databases051 installsUpdated 4w ago
Repository

About drizzle-orm

A Drizzle ORM skill that provides targeted guidance for database schema, migrations, and testing. It is intended for implementation and review workflows, with checks tailored to the affected database surface.

Key features

  1. 01Select guidance for the affected ORM surface
  2. 02Cover schema, JSON columns, and timestamps
  3. 03Keep migration SQL and snapshots consistent
  4. 04Guide database test setup and isolation
  5. 05Check affected database tests against migrations

Use cases

  1. 01Change a schema or JSON column
  2. 02Edit a migration chain
  3. 03Plan database test isolation and atomic writes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/liaoann/skills --skill drizzle-orm

After installing, type/drizzle-ormin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

migrations.md
schema.md
testing.md

Details

From the project README

Drizzle ORM

Apply Drizzle-specific guidance only to the affected surface. Pure application logic with no Drizzle surface does not need this skill. These rules complement the accepted implementation or review workflow, not replace it.

Choose the Relevant Guidance

  • Schema definitions, JSON columns, or timestamps: read schema.md.
  • Schema changes that require migrations, or edits to the migration chain: read migrations.md. Preserve generated SQL and snapshot consistency.
  • Database-test setup, isolation, atomic writes, or schema-test decisions: read testing.md.

A schema change that alters database structure needs both schema and migration guidance. Do not load testing setup merely because a column's TypeScript type changes.

Use test judgment when deciding coverage. Invoke /tdd only if test-first implementation was selected. Driver limitations and project configuration still matter; do not assume all drivers behave alike.

Completion Criterion

The applicable documents' checks are satisfied: generated migration state stays consistent where changed, JSON shapes are explicit, existing timestamp automation is preserved, and affected database tests use the real migration chain without redundant resets or declaration-restating tests. Unaffected surfaces require no incidental edits.

Comments

Markdown supported