sqlalchemy-alembic-expert-best-practices-code-review

Simple, pragmatic, opinionated. Only what matters for writing production-grade SQLAlchemy and Alembic code. Reference these guidelines when: Read individual rule files for detailed explanations and code examples: Each rule file contains: - Writing Alembic migrations for schema changes - Creating or modifying SQLAlchemy models - Adding indexes, constraints, or foreign keys via Alembic - Reviewing database migration code for safety - Refactoring existing database schemas - Optimizing query patterns or database performance - only-concurrent-indexes - Always use postgresql_concurrently=True with autocommit blocks for index operations - verify-query-patterns-are-indexed - Ensure SQLAlchemy queries have appropriate indexes defined - unique-constraint - Split unique constraint creation into concurrent index + constraint steps - split-foreign-key - Add foreign keys with NOT VALID first, then validate separately - change-column-type - Use multi-step approach for column type changes to avoid table locks - split-check-constraint - Add check constraints with NOT VALID first, then validate separately - limit-non-unique-index - Limit non-unique indexes to maximum three columns for efficiency - ensure-index-not-covered - Prevent redundant indexes that are already covered by composite indexes - Brief explanation of why it matters - Impact level and description - Incorrect SQLAlchemy/Alembic...