Name: sqlalchemy-alembic-expert-best-practices-code-review
Author: wispbit-ai

Imported from wispbit-ai/skills (skills/sqlalchemy-alembic-expert-best-practices-code-review/SKILL.md) via skills.sh. Install upstream with npx skills add wispbit-ai/skills --skill sqlalchemy-alembic-expert-best-practices-code-review. Copyright stays with the author (MIT).

SQLAlchemy & Alembic Expert Best Practices

Simple, pragmatic, opinionated. Only what matters for writing production-grade SQLAlchemy and Alembic code.

When to Apply

Reference these guidelines when:

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

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Index Management	CRITICAL-HIGH	`only-concurrent-indexes`, `verify-query-patterns-are-indexed`
2	Constraint Safety	HIGH	`unique-constraint`, `split-foreign-key`, `change-column-type`
3	Optimization	MEDIUM	`split-check-constraint`, `limit-non-unique-index`
4	Index Efficiency	LOW	`ensure-index-not-covered`

Quick Reference

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

How to Use

Read individual rule files for detailed explanations and code examples:

rules/only-concurrent-indexes.md
rules/verify-query-patterns-are-indexed.md
rules/unique-constraint.md
rules/split-foreign-key.md
rules/change-column-type.md
rules/split-check-constraint.md
rules/limit-non-unique-index.md
rules/ensure-index-not-covered.md

Each rule file contains:

Brief explanation of why it matters
Impact level and description
Incorrect SQLAlchemy/Alembic example with explanation
Correct implementation with best practices
Additional context for safe migrations

Install sqlalchemy-alembic-expert-best-practices-code-review and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "wispbit-ai-skills-sqlalchemy-alembic-expert-best-practic-dee862", "kind": "skill", "name": "sqlalchemy-alembic-expert-best-practices-code-review", "description": "SQLAlchemy ORM and Alembic migration best practices for building safe, performant database schemas. This skill should be used when writing, reviewing, or refactoring SQLAlchemy models, Alembic migrations, or database query patterns. Triggers on tasks involving SQLAlchemy ORM, Alembic migrations, database schema changes, or query optimization.", "publisher": "wispbit-ai", "version": "1.0.0", "capabilities": { "domains": [ "data_analysis", "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "SQLAlchemy ORM and Alembic migration best practices for building safe, performant database schemas. This skill should be used when writing, reviewing, or refactoring SQLAlchemy models, Alembic migrations, or database query patterns. Triggers on tasks involving SQLAlchemy ORM, Alembic migrations, database schema changes, or query optimization." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/wispbit-ai/skills", "path": "skills/sqlalchemy-alembic-expert-best-practices-code-review/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/wispbit-ai/skills/sqlalchemy-alembic-expert-best-practices-code-review", "key": "wispbit-ai/skills/skills/sqlalchemy-alembic-expert-best-practices-code-review/SKILL.md" }, "license": "MIT" }, "instructions": "# SQLAlchemy & Alembic Expert Best Practices\n\nSimple, pragmatic, opinionated. Only what matters for writing production-grade SQLAlchemy and Alembic code.\n\n## When to Apply\n\nReference these guidelines when:\n- Writing Alembic migrations for schema changes\n- Creating or modifying SQLAlchemy models\n- Adding indexes, constraints, or foreign keys via Alembic\n- Reviewing database migration code for safety\n- Refactoring existing database schemas\n- Optimizing query patterns or database performance\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------", "cost": { "context_tokens": 590 } }

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

About