Create EF Core migrations for MySQL and SQL Server with separate DbContexts.
npx skills add https://github.com/xin-lai/CodeSpirit --skill db-migration-xin-lai
Please help me install this Agent Skill. Skill: db-migration Source: https://github.com/xin-lai/CodeSpirit/tree/main/.cursor/skills/db-migration Command: npx skills add https://github.com/xin-lai/CodeSpirit --skill db-migration-xin-lai
Ensures consistent database schema changes across MySQL and SQL Server by guiding developers to create, validate, and apply separate EF Core migrations per database while handling database-specific differences and snowflake ID configuration.
Create matching MySQL and SQL Server migrations for your service by running migrations against MySql{Service}DbContext and SqlServer{Service}DbContext and outputting them to Data/Migrations/MySql and Data/Migrations/SqlServer.
High-intent search queries and answers about installing and using this skill.
To create synchronized EF Core migrations, run migration commands against database-specific DbContext types like MySql{Service}DbContext and SqlServer{Service}DbContext, outputting them to separate Data/Migrations directories for each database provider.
The recommended DbContext pattern uses a three-layer inheritance structure with database-specific DbContext types. This separates MySQL and SQL Server configurations while enforcing rules like ValueGeneratedNever for snowflake IDs during EF Core migrations.
Handle snowflake ID configuration in EF Core migrations by enforcing the ValueGeneratedNever option on your entity properties. This ensures both MySQL and SQL Server schemas treat snowflake IDs as application-generated rather than database-generated values.
MySQL EF Core migrations require specific adjustments for datetime mappings, character sets, boolean mappings, and long-text fields. SQL Server needs minimal adjustments compared to MySQL when generating synchronized database migrations.
You can validate and apply EF Core migrations automatically using included PowerShell scripts. These scripts verify migration files and execute database updates against both MySQL and SQL Server targets.
EF Core migrations fail with a single DbContext because MySQL and SQL Server require distinct provider configurations. Using separate database-specific DbContext types ensures correct schema mappings and prevents migration conflicts.
SparkymodManage EF Core migrations across SQL Server and MySQL providers.
johnlindquistAutomate cross-database queries and schema management across SQLite, PostgreSQL, and MySQL.
EmmanuelkwaaGenerate .NET backend entities with EF Core configurations and migrations.
BridgingIT-GmbHAutomate EF Core DbContext setup, migrations, and LINQ queries for .NET applications.
