What problem does it solve? Changing database schema in the autotest backend requires hand-writing Alembic migrations that stay in sync with the async SQLAlchemy models, and mistakes like forgotten model imports, destructive autogenerated drops, or SQLite ALTER limitations can silently corrupt the schema or lose data. ## Core Features & Use Cases - Autogenerated Migrations: Runs alembic revision --autogenerate against the models in backend/src/models/ and guides review of the generated revision file. - SQLite-Specific Safeguards: Handles SQLite limitations such as batch_alter_table requirements, rename-as-drop+add pitfalls, and NOT NULL column backfill strategies. - Safe Apply and Rollback: Enforces pre-flight checks (alembic current, git status) and tests downgrade/upgrade cycles before committing. - Use Case: After adding a new column to a model in backend/src/models/, use this Skill to generate the migration, verify the operations, apply it to the local SQLite database, and confirm rollback works before committing both files together. ## Quick Start Ask the assistant to create and apply an Alembic migration for the model change you just made in backend/src/models/.
