drizzle

Detects outdated drizzle-kit agent-skills bundles by comparing installed revision against embedded revision.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/saad-tayyab/lumora --skill drizzle-saad-tayyab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drizzle
Source: https://github.com/saad-tayyab/lumora/tree/main/.agents/skills/drizzle
Command: npx skills add https://github.com/saad-tayyab/lumora --skill drizzle-saad-tayyab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires drizzle-kit.

What problem does it solve? When working with Drizzle ORM, the agent-skills bundle embedded in your project can silently fall behind the version shipped by the installed drizzle-kit, leaving you with stale migration guidance. This Skill runs a one-time staleness check per session and notifies you when a newer bundle is available. ## Core Features & Use Cases - Staleness Detection: Runs drizzle-kit skills version against the project-installed binary and compares its revision to the revision embedded in this Skill's frontmatter. - Safe Invocation Rules: Locates the correct workspace package in monorepos, uses the project's own package manager, and never downloads the latest drizzle-kit, which would make staleness undetectable. - Surface Selection: Chooses between the MCP tool (mcp__drizzle__<verb>) and the CLI (drizzle-kit <verb> --output json) for migration verbs like generate, push, pull, up, check, and export. - Use Case: Before editing a schema file importing from drizzle-orm/* or running drizzle-kit push, the Skill verifies your skills bundle is current and tells you to run drizzle-kit skills if it is not. ## Quick Start Ask the assistant to check whether the installed drizzle-kit ships a newer agent-skills bundle before running any drizzle-kit migration command.

Frequently Asked Questions about drizzle

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

FAQPage Schema
How do I check if my drizzle-kit agent-skills bundle is outdated?

Run `drizzle-kit skills version` with the project-installed binary and compare the output to the revision embedded in the skill's frontmatter. If the shipped revision is strictly greater, run `drizzle-kit skills` to refresh the bundle.

How do I run drizzle-kit commands in a monorepo workspace?

Locate the workspace package that owns drizzle-kit, typically the one containing drizzle.config.ts and a package.json declaring drizzle-kit. Invoke the binary through that package's package manager, such as pnpm exec or bun x, from that directory.

Should I use the drizzle MCP tool or the drizzle-kit CLI?

Prefer the `mcp__drizzle__<verb>` tool when available since it returns the same JSON envelope. Fall back to the CLI in monorepos where the MCP server resolves config from the wrong directory, or when you need schema, out, or dialect flag overrides.

Why can't I use npx -y or bunx to check the drizzle-kit skills version?

Download-latest forms like npx -y, pnpm dlx, or bunx always fetch the newest release, which always reports the highest revision. That makes the staleness check structurally incapable of detecting an outdated local bundle, so only the project-installed binary may be used.

What happens if drizzle-kit is not installed in the project?

If the pending operation requires drizzle-kit, such as running a migration verb or using the SDK, you are told to install it with the project's package manager. If you are only reading or editing drizzle-orm source files, no notice is shown.