alembic
Database migration management for SQLAlchemy projects using Alembic
Best use case
alembic is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Database migration management for SQLAlchemy projects using Alembic
Database migration management for SQLAlchemy projects using Alembic
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "alembic" skill to help with this workflow task. Context: Database migration management for SQLAlchemy projects using Alembic
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/alembic/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How alembic Compares
| Feature / Agent | alembic | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Database migration management for SQLAlchemy projects using Alembic
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Alembic Database Migrations
Alembic is a database migration tool for SQLAlchemy projects that provides version control for your database schema.
## Quick Start
### Create Migration (Autogenerate)
```bash
# Generate migration from model changes
uv run alembic revision --autogenerate -m "Add user table"
# Check if there are pending changes
uv run alembic check
```
### Apply Migrations
```bash
# Upgrade to latest version
uv run alembic upgrade head
# Upgrade to specific revision
uv run alembic upgrade ae1027a6acf
# Downgrade one revision
uv run alembic downgrade -1
# Downgrade to base (empty schema)
uv run alembic downgrade base
```
### Check Status
```bash
# Show current database revision
uv run alembic current
# Show all revision history
uv run alembic history
# Show revision details
uv run alembic show ae1027a6acf
```
## Common Patterns
### Autogenerate Configuration
**env.py setup for async SQLAlchemy:**
```python
import asyncio
from logging.config import fileConfig
from sqlalchemy import pool
from sqlalchemy.ext.asyncio import async_engine_from_config
from alembic import context
# Import your models
from app.models import Base
from app.config import get_settings
config = context.config
settings = get_settings()
# Configure database URL for async
database_url = settings.database_url.replace("postgresql://", "postgresql+asyncpg://")
config.set_main_option("sqlalchemy.url", database_url)
target_metadata = Base.metadata
async def run_async_migrations():
connectable = async_engine_from_config(
config.get_section(config.config_ini_section, {}),
prefix="sqlalchemy.",
poolclass=pool.NullPool,
)
async with connectable.connect() as connection:
await connection.run_sync(do_run_migrations)
await connectable.dispose()
def do_run_migrations(connection):
context.configure(
connection=connection,
target_metadata=target_metadata,
compare_type=True,
compare_server_default=True,
render_as_batch=False, # Set to True for SQLite
)
with context.begin_transaction():
context.run_migrations()
def run_migrations_online():
asyncio.run(run_async_migrations())
if context.is_offline_mode():
run_migrations_offline()
else:
run_migrations_online()
```
### Manual Migration Operations
**Common schema changes:**
```python
from alembic import op
import sqlalchemy as sa
def upgrade():
# Add column
op.add_column('users', sa.Column('email', sa.String(255), nullable=True))
# Rename table
op.rename_table('old_table', 'new_table')
# Create index
op.create_index('ix_users_email', 'users', ['email'])
# Add constraint
op.create_check_constraint('ck_age_positive', 'users', 'age > 0')
def downgrade():
# Reverse operations
op.drop_constraint('ck_age_positive', 'users')
op.drop_index('ix_users_email')
op.rename_table('new_table', 'old_table')
op.drop_column('users', 'email')
```
### Batch Mode (for SQLite)
**Configure batch mode in env.py:**
```python
context.configure(
connection=connection,
target_metadata=target_metadata,
render_as_batch=True # Required for SQLite migrations
)
```
**Generated batch migration:**
```python
def upgrade():
with op.batch_alter_table('users', schema=None) as batch_op:
batch_op.add_column(sa.Column('email', sa.String(length=255), nullable=True))
batch_op.create_index('ix_users_email', ['email'], unique=False)
```
### Filtering Objects
**Skip certain objects in autogenerate:**
```python
def include_object(object, name, type_, reflected, compare_to):
# Skip temporary tables
if type_ == "table" and name.startswith("temp_"):
return False
# Skip columns with skip_autogenerate flag
if type_ == "column" and not reflected:
if object.info.get("skip_autogenerate", False):
return False
return True
context.configure(
connection=connection,
target_metadata=target_metadata,
include_object=include_object
)
```
**Filter by schema:**
```python
def include_name(name, type_, parent_names):
if type_ == "schema":
return name in [None, "public", "auth"] # Include default + specific schemas
elif type_ == "table":
return parent_names["schema_qualified_table_name"] in target_metadata.tables
return True
context.configure(
connection=connection,
target_metadata=target_metadata,
include_name=include_name,
include_schemas=True
)
```
### Custom Migration Processing
**Modify generated migrations:**
```python
def process_revision_directives(context, revision, directives):
script = directives[0]
# Skip empty migrations
if config.cmd_opts.autogenerate and script.upgrade_ops.is_empty():
directives[:] = []
return
# Remove downgrade operations for one-way migrations
script.downgrade_ops.ops[:] = []
context.configure(
connection=connection,
target_metadata=target_metadata,
process_revision_directives=process_revision_directives
)
```
### Data Migrations
**Migrate data during schema change:**
```python
def upgrade():
# Add new column
op.add_column('users', sa.Column('full_name', sa.String(255), nullable=True))
# Migrate data
connection = op.get_bind()
connection.execute(
sa.text("UPDATE users SET full_name = first_name || ' ' || last_name")
)
# Make column required after data migration
op.alter_column('users', 'full_name', nullable=False)
def downgrade():
op.drop_column('users', 'full_name')
```
### Branch Migrations
**Work with multiple branches:**
```bash
# Create branch
uv run alembic revision -m "Create feature branch" --head=base --branch-label=feature_x
# Upgrade specific branch
uv run alembic upgrade feature_x@head
# Merge branches
uv run alembic merge -m "Merge feature_x into main" feature_x@head main@head
```
## Practical Code Snippets
### Check if Database is Up-to-Date
```python
from alembic import config, script
from alembic.runtime import migration
from sqlalchemy import create_engine
def is_database_up_to_date(alembic_cfg_path, database_url):
"""Check if database schema matches latest migrations"""
cfg = config.Config(alembic_cfg_path)
directory = script.ScriptDirectory.from_config(cfg)
engine = create_engine(database_url)
with engine.begin() as connection:
context = migration.MigrationContext.configure(connection)
current_heads = set(context.get_current_heads())
latest_heads = set(directory.get_heads())
return current_heads == latest_heads
```
### Programmatically Run Migrations
```python
from alembic import command
from alembic.config import Config
def run_migrations(alembic_ini_path):
"""Run all pending migrations"""
alembic_cfg = Config(alembic_ini_path)
command.upgrade(alembic_cfg, "head")
def create_migration(alembic_ini_path, message, autogenerate=True):
"""Create new migration"""
alembic_cfg = Config(alembic_ini_path)
command.revision(alembic_cfg, message=message, autogenerate=autogenerate)
```
### Custom Migration Operations
```python
from alembic.autogenerate import rewriter
from alembic.operations import ops
writer = rewriter.Rewriter()
@writer.rewrites(ops.AddColumnOp)
def add_column_non_nullable(context, revision, op):
"""Add non-nullable columns in two steps"""
if not op.column.nullable:
op.column.nullable = True
return [
op,
ops.AlterColumnOp(
op.table_name,
op.column.name,
nullable=False,
existing_type=op.column.type,
schema=op.schema
)
]
return op
# Use in env.py
context.configure(
connection=connection,
target_metadata=target_metadata,
process_revision_directives=writer
)
```
## Requirements
- **Python 3.8+**: Required for async support
- **SQLAlchemy 2.0+**: For modern async patterns
- **PostgreSQL/MySQL/SQLite**: Supported databases
- **Alembic 1.8+**: Migration tooling
### Common Dependencies
```bash
# Core dependencies
uv add alembic sqlalchemy
# For PostgreSQL with async
uv add asyncpg
# For MySQL with async
uv add aiomysql
# For SQLite (built-in)
# No additional packages needed
```
### Development Setup
```bash
# Initialize Alembic in existing project
uv run alembic init alembic
# Configure env.py for your models
# Edit alembic.ini for database URL
# First migration
uv run alembic revision --autogenerate -m "Initial schema"
uv run alembic upgrade head
```Related Skills
py-alembic-patterns
Alembic migration patterns for PostgreSQL. Use when creating migrations, reviewing autogenerated migrations, or handling schema changes safely.
azure-quotas
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: "check quotas", "service limits", "current usage", "request quota increase", "quota exceeded", "validate capacity", "regional availability", "provisioning limits", "vCPU limit", "how many vCPUs available in my subscription".
raindrop-io
Manage Raindrop.io bookmarks with AI assistance. Save and organize bookmarks, search your collection, manage reading lists, and organize research materials. Use when working with bookmarks, web research, reading lists, or when user mentions Raindrop.io.
zlibrary-to-notebooklm
自动从 Z-Library 下载书籍并上传到 Google NotebookLM。支持 PDF/EPUB 格式,自动转换,一键创建知识库。
discover-skills
当你发现当前可用的技能都不够合适(或用户明确要求你寻找技能)时使用。本技能会基于任务目标和约束,给出一份精简的候选技能清单,帮助你选出最适配当前任务的技能。
web-performance-seo
Fix PageSpeed Insights/Lighthouse accessibility "!" errors caused by contrast audit failures (CSS filters, OKLCH/OKLAB, low opacity, gradient text, image backgrounds). Use for accessibility-driven SEO/performance debugging and remediation.
project-to-obsidian
将代码项目转换为 Obsidian 知识库。当用户提到 obsidian、项目文档、知识库、分析项目、转换项目 时激活。 【激活后必须执行】: 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入规则(默认到 00_Inbox/AI/、追加式、统一 Schema) 3. 执行 STEP 0: 使用 AskUserQuestion 询问用户确认 4. 用户确认后才开始 STEP 1 项目扫描 5. 严格按 STEP 0 → 1 → 2 → 3 → 4 顺序执行 【禁止行为】: - 禁止不读 SKILL.md 就开始分析项目 - 禁止跳过 STEP 0 用户确认 - 禁止直接在 30_Resources 创建(先到 00_Inbox/AI/) - 禁止自作主张决定输出位置
obsidian-helper
Obsidian 智能笔记助手。当用户提到 obsidian、日记、笔记、知识库、capture、review 时激活。 【激活后必须执行】: 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入三条硬规矩(00_Inbox/AI/、追加式、白名单字段) 3. 按 STEP 0 → STEP 1 → ... 顺序执行 4. 不要跳过任何步骤,不要自作主张 【禁止行为】: - 禁止不读 SKILL.md 就开始工作 - 禁止跳过用户确认步骤 - 禁止在非 00_Inbox/AI/ 位置创建新笔记(除非用户明确指定)
internationalizing-websites
Adds multi-language support to Next.js websites with proper SEO configuration including hreflang tags, localized sitemaps, and language-specific content. Use when adding new languages, setting up i18n, optimizing for international SEO, or when user mentions localization, translation, multi-language, or specific languages like Japanese, Korean, Chinese.
google-official-seo-guide
Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation
github-release-assistant
Generate bilingual GitHub release documentation (README.md + README.zh.md) from repo metadata and user input, and guide release prep with git add/commit/push. Use when the user asks to write or polish README files, create bilingual docs, prepare a GitHub release, or mentions release assistant/README generation.
doc-sync-tool
自动同步项目中的 Agents.md、claude.md 和 gemini.md 文件,保持内容一致性。支持自动监听和手动触发。