CtrlK
BlogDocsLog inGet started
Tessl Logo

ef-migration

Generates Entity Framework Core (EF Core) database migrations for C# / .NET projects based on the entity model specification in docs/entity_model.md. Use when the user asks to "create database migration", "add ef migration", "update schema with ef core", "generate db migration for .net", or mentions EF Core, DbContext, or database migrations in C#.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

EF Core Database Migration

Goal

Create a native EF Core C# Migration (dotnet ef migrations add <MigrationName>) and configure entity models in DbContext based on docs/entity_model.md.

Instructions

  1. Read docs/entity_model.md to inspect the required entities, attributes, relationships, and validation constraints.

  2. Inspect existing DbContext and Entity Classes under the project solution (.csproj).

  3. Generate/Update Entity Classes & Configurations:

    • Represent entities as C# classes with file-scoped namespaces and modern properties (public required string Name { get; set; }).
    • Declare navigation properties safely for Nullable Reference Types (e.g. public List<OrderItem> Items { get; set; } = []; or public Customer Customer { get; set; } = null!;).
    • Implement IEntityTypeConfiguration<T> for Fluent API mappings (table names, column types, HasPrecision(18, 2) for decimal fields, HasConversion<string>() for enums, foreign keys, and unique indexes).
    • Register configurations in OnModelCreating(ModelBuilder modelBuilder) (or use modelBuilder.ApplyConfigurationsFromAssembly(...)).
  4. Generate EF Core Migration:

    • Run dotnet ef migrations add UCXXX_Description using CLI. For multi-project solutions, specify project flags (e.g. dotnet ef migrations add UCXXX_Description --project src/MyApp.Data --startup-project src/MyApp.Web).
    • Verify the generated migration class under Migrations/.
  5. DO NOT:

    • Execute destructive schema drops on production environments.
    • Hardcode connection strings in source code; use appsettings.json or environment variables.
  6. Next Step Guidance:

    • Conclude your response by summarizing the migration created and guiding the user to implementation:

    "Next step: Run /implement UC-XXX (e.g. /implement UC-001) to construct your vertical slice feature."

Repository
AI-Unified-Process/marketplace
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.