schema-change-checklist

What problem does it solve? Adding a column to an existing database table touches many layers — Drizzle schema, OpenAPI spec, generated types, route mappers, and upsert clauses — and missing any one causes silent failures where fields never round-trip between the API and the database. ## Core Features & Use Cases - Ordered 10-step checklist: Walks through the Drizzle schema file, push-force migration, openapi.yaml request and response schemas, codegen, toApiItem, toDbValues, onConflictDoUpdate, typecheck, frontend consumers, and tests. - Common-miss catalog: Documents the seven most frequent omissions (e.g. the onConflictDoUpdate SET clause) so upserts do not silently keep stale values. - Additive-push-force constraints: Provides safe patterns for populated tables, such as using uniqueIndex instead of .unique() and avoiding composite primary keys with new columns. - Use Case: When asked to add an isPrep boolean to the mixes table, follow the checklist to update the schema, regenerate Zod types and React Query hooks, and wire the field through every route mapper without silent data loss. ## Quick Start Use the schema-change-checklist skill to add a new column to an existing database table and update all related API layers.