db-schema-change

Routes Postgres schema changes through additive migration, API contract sync, and typecheck guardrails.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill db-schema-change-ravenslight2010
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-schema-change
Source: https://github.com/ravenslight2010/Production-run-calculator/tree/main/.agents/skills/db-schema-change
Command: npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill db-schema-change-ravenslight2010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Modifying a production Postgres schema risks data loss, broken API contracts, and type errors rippling across the codebase. This Skill routes every Drizzle schema change through the correct procedure so migrations stay additive, generated clients stay in sync, and stored data is never silently invalidated. ## Core Features & Use Cases - Change Routing: Directs field/column additions on existing tables to the canonical schema-change-checklist procedure, while handling new tables and other schema changes through shared guardrails. - Contract Synchronization: Enforces updating both request and response OpenAPI shapes, then regenerating checked-in Zod and React Query clients without hand-editing generated output. - Safe Migration & Data Healing: Requires additive-only changes on populated tables, push-force schema application instead of hand-written SQL, and routing to a data-heal playbook when existing rows are affected. - Use Case: When adding a nullable column to a production table, follow the routed checklist to update the Drizzle schema, regenerate API clients, run typechecks, and push the schema without touching live data destructively. ## Quick Start Ask the AI to add a new column to an existing Drizzle table and route the change through the schema change procedure with typechecks and push-force migration.

Frequently Asked Questions about db-schema-change

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

FAQPage Schema
When is a data heal needed after a schema change?

A data heal is needed when the change repairs or invalidates existing profiles, pools, or day-state. Route to the data-heal-playbook, plan a marker-guarded heal, and communicate what will change live, since a schema edit alone does not repair data.