migration-workflow

Guides EF Core migrations and rollback with build-and-test verification.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill migration-workflow-trossitec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-workflow
Source: https://github.com/Trossitec/dotnet-claude-kit/tree/main/skills/migration-workflow
Command: npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill migration-workflow-trossitec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrations and dependency or .NET version upgrades often fail in production because they are applied without review, lack a rollback plan, and skip verification steps.

Core Features & Use Cases

  • EF Core migration safety workflow: review generated SQL via idempotent migration scripts, watch for data-loss operations, and verify after applying.
  • Rollback-first operational guidance: provides explicit rollback commands and a “remove failed migration” strategy when something goes wrong.
  • Incremental NuGet and .NET upgrade process: updates packages or target frameworks one change at a time, with build-and-test checkpoints to isolate breakages.
  • Use case: You need to rename a column and add an index on a large table while updating packages; this skill helps you script, review, apply, test, and roll back safely.

Quick Start

Ask the AI to give you a safe step-by-step EF Core and NuGet migration workflow for your repo and include the exact verification and rollback steps.

Frequently Asked Questions about migration-workflow

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

FAQPage Schema
What is the safest way to apply EF Core database migrations during a NuGet upgrade?

The safest EF Core migration workflow involves generating idempotent SQL scripts, reviewing the output for data-loss operations, applying the update, and verifying with tests before proceeding to the next incremental package upgrade step.

How do I rollback a failed EF Core migration after applying it to the database?

To rollback a failed EF Core migration, use the dotnet ef database update command to target the previous migration state, then remove the failed migration. This rollback-first strategy ensures you can revert safely when something goes wrong.

Why should I review idempotent migration scripts before applying EF Core database updates?

Reviewing idempotent migration scripts is necessary to catch data-loss operations before they reach production. This EF Core migration review step prevents destructive schema changes and ensures the generated SQL output matches your intended database update.

How do I upgrade NuGet packages and .NET target frameworks without breaking my build?

To upgrade NuGet packages and .NET target frameworks safely, apply one change at a time and enforce build-and-test verification checkpoints between each incremental upgrade step to isolate breakages and ensure stability.

Can I rename a column and add an index on a large table safely with EF Core?

Yes, you can rename a column and add an index safely by following the EF Core migration workflow: script the changes, review the generated SQL for data loss, apply the database update, run tests, and prepare a rollback plan.

What are the limitations of applying EF Core migrations without test verification?

Applying EF Core migrations without test verification risks production failures because it skips detecting breakages, lacks a rollback strategy, and ignores potential data-loss operations hidden in the generated SQL output.