hf.enforce-migrations

You can enforce Alembic migrations by using a PreToolUse hook that intercepts Edit and Write operations, evaluating file paths and content to block direct DDL statements outside migration files. This guardrail automatically rejects risky changes and redirects developers to create new migration stubs, preserving versioned schemas and audit trails.

Preventing database drift is best achieved by enforcing migration-based workflows that block direct schema modifications. A PreToolUse hook validates that all DDL operations reside strictly within Alembic migration files, rejecting non-migration edits and instructing developers to generate proper migration stubs.

Yes, you can use a PreToolUse hook to intercept and validate DDL statements before they are written. The hook evaluates file paths and content during Edit and Write operations across code and SQL-related files, blocking direct DDL outside migrations and ensuring schema changes go through Alembic.

Yes, this migration enforcement guardrail works with both code and SQL files. It operates as a PreToolUse hook across Edit and Write operations, evaluating the file path and content to detect and block DDL statements in any non-migration files, ensuring all schema changes use Alembic migrations.

When you attempt a direct database schema change outside an Alembic migration, the PreToolUse hook blocks the operation and rejects the DDL statement. It then instructs you to create a new Alembic migration stub, ensuring the change is tracked and preventing risky untracked deployments.