database-migration

Manage database schema changes with Alembic migrations for SQLAlchemy models.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Euda1mon1a/Autonomous-Assignment-Program-Manager --skill database-migration-euda1mon1a
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: database-migration
Source: https://github.com/Euda1mon1a/Autonomous-Assignment-Program-Manager/tree/main/.claude/skills/database-migration
Command: npx skills add https://github.com/Euda1mon1a/Autonomous-Assignment-Program-Manager --skill database-migration-euda1mon1a

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides expert guidance for managing database schema changes, ensuring data integrity and preventing common migration pitfalls.

Core Features & Use Cases

  • Schema Evolution: Safely add, modify, or remove database tables and columns.
  • Migration Management: Generate, review, and test Alembic migrations for SQLAlchemy models.
  • Data Integrity: Implement strategies for data backfilling and constraint management.
  • Use Case: When adding a new middle_name field to your Person model, this Skill guides you through creating the necessary Alembic migration, testing the upgrade and downgrade paths, and committing the changes safely.

Quick Start

Use the database-migration skill to add a nullable 'middle_name' column to the 'persons' table.

Frequently Asked Questions about database-migration

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

FAQPage Schema
How do I safely add a new column to an existing SQLAlchemy database schema?▼

To safely add a column to a SQLAlchemy database schema, generate an Alembic migration, test the upgrade and downgrade paths, and apply the modification to ensure data integrity and prevent common migration pitfalls.

How do I roll back a database migration if something goes wrong?▼

Rolling back a database migration requires using Alembic's downgrade functionality to safely reverse schema modifications, drop added columns or indexes, and restore the previous database state while maintaining data integrity.

What is the best way to manage data backfilling during a schema migration?▼

The best way to manage data backfilling during a schema migration is to implement constraint management strategies alongside Alembic migrations, ensuring existing records are correctly populated when adding or modifying database columns.

How do I create indexes and manage foreign key constraints using Alembic?▼

Creating indexes and managing foreign key constraints using Alembic involves generating migration scripts that explicitly define these schema modifications, facilitating safe database evolution and ensuring relational data integrity.

Do I need SQLAlchemy models to use Alembic for database migrations?▼

Yes, you need SQLAlchemy models to use Alembic for database migrations, as the migration management process relies on comparing these models against the existing database schema to generate accurate upgrade and downgrade scripts.