// Drizzle ORM database migration workflow for packages that still use Drizzle (agents, example). Do NOT use for apps/os — that app uses sqlfu/D1.
Create a new Cloudflare app in this repo with the expected package scripts, Doppler shape, and CI workflow wiring.
Query and analyze Cloudflare Workers traces through the general Cloudflare API MCP server. Use when diagnosing Workers traces, distributed tracing spans, observability events, subrequest chains, or when an agent needs Cloudflare trace data programmatically.
Debug MCP servers with the official MCP Inspector UI and CLI. Use when an MCP server will not connect, auth fails, tools/resources/prompts are missing, or a tool call needs to be reproduced outside Codex/Claude.
Monitoring workflow for architect: Cloudflare Worker checks, task updates, and Slack escalation.
Debug failures in the Cloudflare OS worker using the Cloudflare MCP server. Use when diagnosing 500s, missing logs, or request-level regressions in production or preview.
PostHog alert responder workflow with required Slack deep-links and escalation rules.
| name | drizzle-migrations |
| description | Drizzle ORM database migration workflow for packages that still use Drizzle (agents, example). Do NOT use for apps/os — that app uses sqlfu/D1. |
Use this skill only for packages that still ship Drizzle schema + migrations.
Do not use for apps/os. OS schema lives in apps/os/src/db/definitions.sql; run pnpm --dir apps/os sqlfu:generate / sqlfu:migrate instead.
Example paths:
apps/agents/src/db/schema.tsapps/example/src/db/schema.tsFrom the package directory:
pnpm drizzle-kit generate --name descriptive_migration_name
.sqlYou may edit generated SQL for backfills. Never edit _journal.json or *_snapshot.json by hand.
pnpm drizzle-kit check
pnpm drizzle-kit migrate
See docs/fixing-drizzle-migration-conflicts.md.
drizzle-kit generatepnpm os db:migrate — legacy OS app removedapps/os sqlfu migrations