migration-workflow

Execute EF Core schema migrations with SQL review, rollback, and verification.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/shahdanish/vibepos --skill migration-workflow-shahdanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-workflow
Source: https://github.com/shahdanish/vibepos/tree/main/skills/migration-workflow
Command: npx skills add https://github.com/shahdanish/vibepos --skill migration-workflow-shahdanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken EF Core migrations and risky dependency/.NET upgrades by enforcing a review-first, incremental, test-backed workflow with a clear rollback plan.

Core Features & Use Cases

  • Review before applying: Generate and inspect migration SQL (including idempotent scripts) to catch data loss, destructive operations, and long locks early.
  • Rollback-ready execution: Plan and perform controlled rollbacks using EF Core migration targeting and safe package/version recovery strategies.
  • Incremental upgrades: Update one package (or target framework) at a time, build and test between steps to quickly identify the breaking change.
  • EF Core best practices: Use descriptive migration names, enforce one logical change per migration, and handle potential data-loss scenarios explicitly via migration code and SQL.

Quick Start

Ask the AI to produce an EF Core migration and update plan for your project by having it guide you through checking the current migration state, generating a reviewable SQL script, applying the migration in the correct environment, and running verification tests with a rollback path.

Frequently Asked Questions about migration-workflow

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

FAQPage Schema
How do I safely rollback an EF Core database migration?

The migration-workflow approach ensures a safe rollback by using EF Core migration targeting to revert schema updates to a specific previous migration state. It enforces planning a controlled rollback procedure before applying any changes to development or staging databases.

What is the best way to review generated SQL before applying EF Core migrations?

The best way to review EF Core migrations is to generate and inspect idempotent SQL scripts before applying updates. This review-first workflow catches data loss, destructive operations, and long locks early, ensuring explicit handling of potential schema issues.

How do I handle data-loss warnings during a dotnet upgrade and database migration?

Handling data-loss warnings during database migration requires explicit management via migration code and SQL review. You must inspect generated SQL scripts to identify destructive operations and address data-loss scenarios before applying updates to staging databases.

Can I update multiple NuGet packages at once during a .NET target framework upgrade?

Incremental .NET upgrades require updating one NuGet package or target framework at a time. Running build and test verification between each step isolates breaking changes quickly, preventing widespread dependency conflicts during dotnet upgrades.

Why do I need to run verification tests after applying a database migration?

Post-change build and test verification confirms that EF Core schema updates and NuGet updates function correctly without breaking existing application logic. This test-backed workflow validates stability before finalizing upgrades and ensures a safe rollback path if tests fail.

When should I use idempotent SQL scripts for EF Core migrations?

Idempotent SQL scripts are essential during EF Core migration review to safely apply schema updates across different database states. Including them in your workflow prevents duplicate operations and ensures consistent deployment to development and staging environments.