cck-migration-workflow

Apply EF Core migrations with SQL review, rollback plans, and test verification.

2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/s205109/AHKFlowApp --skill cck-migration-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cck-migration-workflow
Source: https://github.com/s205109/AHKFlowApp/tree/main/.claude/skills/cck-migration-workflow
Command: npx skills add https://github.com/s205109/AHKFlowApp --skill cck-migration-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a safe, repeatable workflow to create, review, apply, and roll back EF Core database migrations, update NuGet dependencies, and upgrade .NET versions without causing data loss or production downtime.

Core Features & Use Cases

  • Migration safety: Generate and review SQL scripts, detect data-loss operations, and apply staged schema changes to preserve data.
  • Rollback & verification: Define rollback plans, run full unit and integration tests after changes, and remove failed migrations from code if necessary.
  • Incremental dependency and framework upgrades: Audit packages, update incrementally by semantic version category, and migrate target frameworks with centralized configuration and checklist guidance.
  • Use Case: Prepare and apply a schema change plus a package upgrade in a service migrating to .NET 10 while ensuring automatic verification and a clear rollback path.

Quick Start

Create a descriptive EF Core migration, generate and review the SQL script for potential data loss, and prepare a rollback plan before applying the migration and running the full test suite.

Frequently Asked Questions about cck-migration-workflow

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

FAQPage Schema
How do I safely apply EF Core database migrations without causing data loss?

To apply EF Core database migrations safely, generate and review the SQL script for data-loss operations, maintain a one-change-per-migration discipline, and prepare a rollback plan before applying staged schema changes.

What is the best way to roll back a failed EF Core migration in a .NET project?

The best way to roll back a failed EF Core migration is to define a rollback plan beforehand, remove the failed migration from code if necessary, and execute full unit and integration tests to verify database integrity.

How do I incrementally upgrade NuGet packages and migrate to a new .NET SDK version?

To incrementally upgrade NuGet packages and migrate .NET SDK versions, audit packages, update by semantic version category, migrate target frameworks using centralized configuration, and follow a checklist for verification.

Does this migration workflow support integration testing in CI pipelines for .NET projects?

Yes, this workflow supports integration testing in CI pipelines for .NET projects by running full unit and integration tests after applying migrations, package updates, or SDK upgrades to ensure safe and repeatable deployments.

Why should I review generated SQL scripts before applying EF Core migrations?

Reviewing generated SQL scripts before applying EF Core migrations is necessary to detect potential data-loss operations, ensure staged schema changes preserve data, and validate that the one-change-per-migration discipline is maintained.