alembic-migrations

Automate Alembic database schema migrations across multiple SQLAlchemy databases.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/koenvorster/Personal_project_VorstersNV --skill alembic-migrations-koenvorster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alembic-migrations
Source: https://github.com/koenvorster/Personal_project_VorstersNV/tree/main/.claude/skills/alembic-migrations
Command: npx skills add https://github.com/koenvorster/Personal_project_VorstersNV --skill alembic-migrations-koenvorster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Alembic migrations are essential for evolving VorstersNV's databases across multiple environments, including a main schema and a separate analytics schema, while keeping migrations trackable and reversible.

Core Features & Use Cases

  • Supports multiple Alembic configurations (eg. alembic.ini for the main database and alembic_analytics.ini for analytics) and clear instructions to select the correct config with -c.
  • Provides guidelines for the usual migration workflow: generate revisions, apply upgrades, and perform downgrades with a consistent naming convention.
  • Includes an asynchronous environment setup example and a robust migration pattern for evolving tables and columns safely.

Quick Start

Run an Alembic upgrade to apply pending migrations and verify the migration history against the target database.

Frequently Asked Questions about alembic-migrations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Alembic migrations for multiple database schemas?

Managing Alembic migrations across multiple schemas requires separate configuration files, such as alembic.ini for the main database and alembic_analytics.ini for analytics, using the -c flag to target the correct schema during upgrades and downgrades.

How do I configure async SQLAlchemy engines in an Alembic environment?

Configuring async SQLAlchemy engines in an Alembic environment involves setting up an asynchronous environment example within your migration scripts to safely handle database connections during schema changes.

What is the workflow for generating and applying Alembic database upgrades?

The Alembic upgrade workflow involves generating revision files, applying upgrades to pending migrations, and performing downgrades using a consistent naming convention to keep database schema changes trackable and reversible.

Do I need separate Alembic configuration files for main and analytics schemas?

Yes, separate Alembic configuration files are needed for main and analytics schemas, allowing you to select the correct configuration with the -c flag to target the appropriate database environment safely.

How do I safely evolve tables and columns during a database schema upgrade?

To safely evolve tables and columns during a database schema upgrade, apply a robust migration pattern that ensures changes are trackable and reversible, verifying migration history against the target database afterwards.