generate-migration

Generate and apply EF Core migrations for Coalesce projects.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/IntelliTect/IntelliPlugins --skill generate-migration-intellitect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-migration
Source: https://github.com/IntelliTect/IntelliPlugins/tree/main/plugins/coalesce-accelerator/skills/generate-migration
Command: npx skills add https://github.com/IntelliTect/IntelliPlugins --skill generate-migration-intellitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end process of generating and applying EF Core migrations in a Coalesce project after changes to entity models or DbContext.

Core Features & Use Cases

  • Generate and name EF Core migrations describing the change
  • Regenerate Coalesce artifacts to keep the API and TypeScript types in sync
  • Apply the migration to the database and run tests to validate changes

Quick Start

After updating your Coalesce entity models, run this skill to generate a new EF Core migration and apply it to your target database.

Frequently Asked Questions about generate-migration

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

FAQPage Schema
How do I generate EF Core migrations for a Coalesce project after updating entity models?

To generate EF Core migrations for a Coalesce project, you compile changes to your entity models or DbContext, regenerate Coalesce artifacts to sync API and TypeScript types, and use dotnet ef tooling to create and apply the migration to your database.

What do I need to run EF Core migrations in a Coalesce environment?

Running EF Core migrations in a Coalesce environment requires a valid DataProject and StartupProject context, along with .NET tooling including the dotnet ef tool, to properly generate, review, and apply database updates.

Does generating EF Core migrations regenerate Coalesce artifacts to keep TypeScript types in sync?

Yes, generating EF Core migrations includes a Coalesce generation step that regenerates artifacts to keep the API and TypeScript types synchronized with your updated entity models before applying changes to the database.

What is the best way to apply EF Core database migrations and validate the changes?

The best way to apply EF Core database migrations is to use an automated process that creates the migration, regenerates Coalesce artifacts, updates the target database, and runs tests to validate the changes across data and web projects.

Why does my Coalesce EF Core migration workflow require both a DataProject and StartupProject?

Your Coalesce EF Core migration workflow requires both a DataProject and StartupProject context so the dotnet ef tooling can accurately target the correct database configuration and apply updates across both data and web projects.