migration-workflow

Generate EF Core migration workflows with idempotent SQL and rollback plans.

640|145|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill migration-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-workflow
Source: https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/migration-workflow
Command: npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill migration-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a consistent, safety-first process for applying EF Core database migrations, updating NuGet dependencies, and upgrading .NET versions to minimize data loss, downtime, and regressions.

Core Features & Use Cases

  • Review before apply: Emphasizes generating and auditing idempotent SQL scripts and checking for data-loss or long-lock operations before applying migrations.
  • Rollback planning: Documents explicit rollback steps for migrations, package updates, and framework upgrades so teams can recover quickly from failures.
  • Incremental updates & verification: Encourages one-change-per-migration, one-package-at-a-time updates, and build-and-test validation including integration tests to catch real-world issues.
  • .NET upgrade checklist: Guides updating global.json, target frameworks, package compatibility, and adopting new runtime features with a phased verification strategy.
  • Use Case: Safely add a new nullable-to-non-nullable column by creating a migration that adds a nullable column, backfills data, then flips the column and removes the old one while preserving rollback and test steps.

Quick Start

Create an EF Core migration named AddOrderShippingAddress, generate the idempotent SQL script for review, run the full test suite including integration tests, and produce a clear rollback plan.

Frequently Asked Questions about migration-workflow

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

FAQPage Schema
How do I safely upgrade .NET versions and NuGet packages without breaking my build?

Safely upgrade .NET versions and NuGet packages by applying one-change-per-migration, one-package-at-a-time updates, and build-and-test validation. This incremental approach with verification steps minimizes regressions and downtime.

What is the best way to generate and review EF Core database migration scripts before applying them to production?

The best way to handle EF Core database migration is to generate and audit idempotent SQL scripts for data-loss or long-lock operations before applying them. This review-before-apply process ensures safe production deployments.

How do I create an EF Core migration to add a non-nullable column without losing existing data?

To add a non-nullable column safely, create a migration that adds a nullable column, backfills existing data, then flips the column and removes the old one. Include integration tests and explicit rollback steps.

Does this migration workflow support creating explicit rollback plans for failed database migrations?

Yes, the migration workflow supports creating explicit rollback plans for failed database migrations, NuGet package updates, and framework upgrades. It documents recovery steps so teams can quickly restore systems after failures.

What should be included in a .NET upgrade checklist to ensure a phased verification strategy?

A .NET upgrade checklist should include updating global.json, target frameworks, checking package compatibility, and adopting new runtime features. This phased verification strategy ensures build-and-test validation at each incremental step.