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

Malicious tool definition detected

Tool: SKILL.md Description: --- name: sqlalchemy-alembic-expert-best-practices-code-review description: SQLAlchemy ORM and Alembic migration best practices for building safe, performant database schemas.

Malicious tool definition detected

Tool: rules/change-column-type.md Description: --- title: Change column types safely in SQLAlchemy impact: HIGH impactDescription: Prevents table locks and downtime during column type changes tags: postgresql, mysql, sqlalchemy, alembic, migrations, schema-changes --- When changing a column type that requires a table rewrite, follow these steps: 1.

Malicious tool definition detected

Tool: rules/ensure-index-not-covered.md Description: --- title: Ensure index is not already covered in SQLAlchemy impact: LOW impactDescription: Prevents redundant indexes and reduces storage costs tags: postgresql, sqlalchemy, alembic, migrations, indexes, optimization --- Ensure that individual column indexes in SQLAlchemy are not covered by existing composite indexes.

Malicious tool definition detected

Tool: rules/limit-non-unique-index.md Description: --- title: Limit non unique indexes in SQLAlchemy impact: MEDIUM impactDescription: Improves index efficiency and reduces storage overhead tags: postgresql, sqlalchemy, alembic, migrations, indexes, performance --- Limit non-unique indexes to a maximum of three columns in PostgreSQL databases: Bad: ```python def upgrade(): with op.get_context().autocommit_block(): op.create_index( 'index_users_on_multiple_columns', 'users',

Malicious tool definition detected

Tool: rules/only-concurrent-indexes.md Description: --- title: Only concurrent indexes in SQLAlchemy impact: CRITICAL impactDescription: Prevents blocking writes during index creation and deletion tags: postgresql, sqlalchemy, alembic, migrations, indexes --- When creating or dropping indexes in PostgreSQL using SQLAlchemy migrations, always use the `postgresql_concurrently=True` option within an autocommit block.

Malicious tool definition detected

Tool: rules/split-check-constraint.md Description: --- title: Add check constraints safely in SQLAlchemy impact: MEDIUM impactDescription: Prevents blocking writes during constraint validation tags: postgresql, sqlalchemy, alembic, migrations, constraints --- When adding check constraints that could affect large tables, create the constraint with `NOT VALID` first to avoid blocking writes during the validation scan.

Malicious tool definition detected

Tool: rules/split-foreign-key.md Description: --- title: Add foreign keys safely in SQLAlchemy impact: HIGH impactDescription: Avoids blocking writes on both tables during foreign key validation tags: postgresql, sqlalchemy, alembic, migrations, foreign-keys --- When adding foreign keys in SQLAlchemy migrations, split the operation into two steps to avoid blocking writes on both tables: 1.

Malicious tool definition detected

Tool: rules/unique-constraint.md Description: --- title: Add unique constraints safely in SQLAlchemy impact: HIGH impactDescription: Prevents blocking reads and writes during constraint creation tags: postgresql, sqlalchemy, alembic, migrations, constraints --- When adding unique constraints that could affect large tables, create the unique index concurrently first to avoid blocking reads and writes during the migration.

Malicious tool definition detected

Tool: rules/verify-query-patterns-are-indexed.md Description: --- title: Verify query patterns are covered by an index in SQLAlchemy impact: HIGH impactDescription: Prevents full table scans and improves query performance tags: postgresql, sqlalchemy, alembic, migrations, indexes, performance --- Ensure that SQLAlchemy query patterns are covered by appropriate database indexes.