Menu
Add an EF Core database migration with auto-detection of the migrations project, startup project, and DbContext. Reports generated and modified files and warns on empty migrations.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Generate integration tests for a concrete API controller derived from UmbrellaGenericRepositoryDataServiceApiController (Pattern 2, backing controller service), covering every testable response status code per endpoint including ExistsById and TotalCount. Resolves enablement and authorization flags on the backing data service. Use after integration test infrastructure exists.
Generate integration tests for a concrete API controller derived from UmbrellaGenericRepositoryApiController (Pattern 1, direct repository), covering every testable response status code per endpoint: success paths, 401/403 authorization, 404, 405 disabled endpoints, 409 concurrency via stamp rotation, 400/422 validation, and optional 500. Use after integration test infrastructure exists.
Generate integration tests for custom API controllers built on the three endpoint-less Umbrella bases, deriving per-action response status contracts per variant: UmbrellaDataAccessApiController (protected data-access helper composition), UmbrellaDataServiceApiController (ExecuteOperationAsync over a data service), and UmbrellaApiController (hand-rolled status helper enumeration). The testing counterpart of umbrella-dotnet-scaffold-custom-api-controller.
Scaffold ASP.NET Core controller integration test infrastructure into an existing or newly created .NET test project using Umbrella.Testing.AspNetCore: concrete local and SQL Server/Azurite Testcontainers WebApplicationFactory classes, xUnit collections, test authentication, config overrides, Program hook, and a minimal smoke test. Use after auditing the server app or when adding WebApplicationFactory-based integration tests.
Analyze, set up, or update .NET test project configuration across a solution to follow the shared Umbrella IsTestProject=true pattern, singular .Test naming, and xUnit v3 Microsoft Testing Platform conventions.
Analyze, set up, or update .NET test project configuration across a solution to follow the shared Umbrella IsTestProject=true pattern, singular .Test naming, and xUnit v3 Microsoft Testing Platform conventions.
Based on SOC occupation classification
| name | umbrella-dotnet-add-ef-migration |
| description | Add an EF Core database migration with auto-detection of the migrations project, startup project, and DbContext. Reports generated and modified files and warns on empty migrations. |
This skill adds EF Core migrations consistently without running dotnet ef migrations add by hand.
scripts\Invoke-AddEfMigration.ps1-MigrationName (required) — name for the new migration; use semantic versioning to match existing migrations (e.g. 1.0.20)-RepoRoot (optional) — defaults to git repository root-MigrationsProject (optional) — relative path to the .Migrations.csproj; auto-detected if omitted-StartupProject (optional) — relative path to the Web SDK startup .csproj; auto-detected if omitted-Context (optional) — DbContext class name; auto-detected via dotnet ef dbcontext list if omittedMigration names must use semantic versioning to match the existing migration history (e.g. 1.0.20). Before running the script, inspect the existing files in the Migrations folder to find the current highest version and use the next increment.
Migrations folder to determine the current highest version number.-MigrationName.dotnet ef --json output, then normalizes whitespace and applies the repository's IDE0005/IDE0058/IDE0161 generated-migration style.Add a migration (auto-detected projects):
powershell -ExecutionPolicy Bypass -File .github\skills\umbrella-dotnet-add-ef-migration\scripts\Invoke-AddEfMigration.ps1 -MigrationName 1.0.20
Add a migration (explicit projects):
powershell -ExecutionPolicy Bypass -File .github\skills\umbrella-dotnet-add-ef-migration\scripts\Invoke-AddEfMigration.ps1 `
-MigrationName 1.0.20 `
-MigrationsProject "Core\MyApp.Core.Data.Migrations\MyApp.Core.Data.Migrations.csproj" `
-StartupProject "Web\MyApp.Web.Server\MyApp.Web.Server.csproj" `
-Context MyAppDbContext
New files: — the .cs and .Designer.cs migration filesModified files: — the *ModelSnapshot.cs filemigrationBuilder callsBefore finishing, read .ai-shared\bundles\umbrella\analyzer-compatibility.md and build the affected projects with their installed analyzers enabled. Treat diagnostics introduced by the generated or changed code as defects in this workflow.
dotnet ef migrations add directly..ai-shared\ and keep this folder as a thin wrapper.