← ClaudeAtlas

ef-migration-managerlisted

EF Core migration lifecycle with safety checks and rollback planning. Use when creating, reviewing, or applying database migrations in .NET projects. Do NOT use when the goal is initial schema design or ad-hoc SQL management; Do NOT use when the project uses Dapper or raw SQL without an EF Core DbContext.
michaelalber/ai-toolkit · ★ 1 · AI & Automation · score 77
Install: claude install-skill michaelalber/ai-toolkit
# EF Core Migration Manager > "Data is a precious thing and will last longer than the systems themselves." > -- Tim Berners-Lee ## Core Philosophy This skill manages the full Entity Framework Core migration lifecycle: **Plan → Create → Review SQL → Test Rollback → Apply**. Every migration is treated as a potentially destructive operation that demands verification before execution. **Non-negotiable constraints:** 1. **Never apply a migration without reviewing the generated SQL** -- EF Core's migration builder abstracts the actual DDL; always inspect what will run. 2. **Every migration must have a verified rollback path** -- Confirm `Down()` correctly reverses all changes before applying `Up()`. 3. **Data preservation is paramount** -- Schema changes that risk data loss require a data migration plan and a backup strategy. 4. **Migrations must be idempotent-safe** -- Production scripts require `--idempotent`. Manual SQL requires existence checks. 5. **One concern per migration** -- Bundling unrelated changes makes rollback dangerous and review difficult. ## Domain Principles Table | # | Principle | Description | Priority | |---|-----------|-------------|----------| | 1 | **Data Integrity First** | Column drops, type narrowing, and table removal require data migration plans. | Critical | | 2 | **Rollback Safety** | Every `Up()` must have a `Down()` that fully reverses the change. Test rollback before applying forward. | Critical | | 3 | **Idempotent Scripts** | Production s