database-migration

The migration workflow detects schema.ts changes and guides you through generating, reviewing SQL, testing locally, and committing migrations while enforcing safety constraints like mandatory user confirmation before each stage.

No, manually editing migration files is strictly prohibited. The workflow enforces safety constraints by requiring user-driven generation prompts and mandatory review checkpoints to maintain auditability and prevent unsafe database schema changes.

The workflow involves modifying server/database/schema.ts, detecting changes, generating migration files, reviewing SQL output, testing locally, and committing schema and migrations together to maintain auditability and prevent risky schema changes.

No, it never auto-runs generation. The process enforces a strict, user-driven workflow with generation prompts and mandatory user confirmation before each stage to ensure safe, review-driven migration generation.

Database schema changes are risky because they can introduce errors. Review checkpoints help by requiring you to vet generated SQL and test locally before committing, ensuring schema.ts changes are properly transformed into safe migration files.

You need this workflow whenever updating server/database/schema.ts or introducing new tables and columns. It ensures changes are properly transformed into vetted migration files and maintains auditability through review-driven generation.