What problem does it solve? Database schema changes often break production because migrations are applied inconsistently, lack rollback paths, or drift from the baseline schema. This Skill enforces a disciplined migration workflow so every schema change is reversible, linted, and verified against the baseline. ## Core Features & Use Cases - Timestamped migration authoring: Creates YYYYMMDDTHHMMSS_<kebab-name>.sql files with mandatory paired .down.sql rollback files, keeping the baseline as the rollback floor. - Baseline synchronization: Keeps db/schema.sql current so a fresh database and a fully migrated database converge to the same schema. - Lint and smoke testing: Runs scripts/lint_migrations.py for filename, pairing, and uniqueness checks, plus scripts/test_migrations_apply.sh to verify triggers and functions actually fire on a fresh database. - Use Case: When renaming a column referenced by a trigger function, the Skill guides you to write the up/down migration pair, sync the baseline, and add an exercise line to the smoke test so PL/pgSQL body bugs are caught before production. ## Quick Start Ask the agent to add a new database migration for your schema change, including the paired down migration and an updated db/schema.sql baseline.
