---
name: feedback-sql-changes
description: SQL changes should be written to separate files for execution and version control
metadata:
Always write SQL schema changes to separate .sql files in the project root directory.
Why: The user needs standalone SQL files for database migration execution and version tracking. Embedding SQL in conversation responses makes it harder to execute and track changes.
How to apply: When making any database structure changes (ALTER TABLE, CREATE TABLE, ADD COLUMN, etc.), create a descriptive .sql file in the project root with clear comments explaining the change. File naming format: action_description_date.sql or add_fieldname_field.sql.
