What problem does it solve?
Changing SQLite schemas in Compozy requires keeping declarative schema sources, Goose migrations, Atlas checksums, sqlc output, and migration tests perfectly synchronized, and any drift or edited history can corrupt production databases.
Core Features & Use Cases
- Append-only migration authoring: Classify the owning stream (global, memory, session, workspace), edit the declarative schema source, and let
make codegen append the next gap-free Goose migration with refreshed atlas.sum.
- Decision matrix and templates: Reference docs classify every change type (columns, indexes, constraints, seed data) and define the owner directory shape for schema sources and migrations.
- Test contract enforcement: Canonical suites cover fresh apply, reopen with preserved data, ahead-version refusal, checksum drift, and migrations-to-declarative-schema equivalence.
- Use Case: When adding a NOT NULL column to a table under
internal/store, follow the procedure to update the declarative schema, run codegen, extend the owner test suite, and verify with make gate before pushing.
Quick Start
Ask the agent to add a new nullable column to a table in internal/store and generate the corresponding Goose migration with updated tests.
