dotnet-scaffold-ef-repository

Scaffold repository interface, implementation, IncludeMap, and DI registration for EF Core entities.

8|1|Updated Feb 5, 2018
One-click install
npx skills add https://github.com/umbrella-libraries/Umbrella --skill dotnet-scaffold-ef-repository
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-scaffold-ef-repository
Source: https://github.com/umbrella-libraries/Umbrella/tree/main/.ai-shared/skills/dotnet-scaffold-ef-repository
Command: npx skills add https://github.com/umbrella-libraries/Umbrella --skill dotnet-scaffold-ef-repository

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold a repository interface, implementation, IncludeMap, and DI registration for an existing EF Core entity, following Umbrella GenericDbRepository patterns.

Core Features & Use Cases

  • Provides a reusable scaffolding pattern for repository layers in Umbrella applications.
  • Ensures IncludeMap and DI wiring are generated consistently across entities.
  • Facilitates rapid onboarding of new EF Core entities into the data access layer.

Quick Start

Run the scaffold tool with the target EF Core entity to generate the repository, interface, IncludeMap, and DI wiring.

Frequently Asked Questions about dotnet-scaffold-ef-repository

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

FAQPage Schema
How do I scaffold an EF Core repository with IncludeMap and DI registration?

To scaffold an EF Core repository, run the scaffold tool against an existing entity to generate the repository interface, implementation, IncludeMap, and DI wiring aligned to Umbrella's GenericDbRepository conventions.

What is an IncludeMap in a GenericDbRepository pattern?

An IncludeMap in the GenericDbRepository pattern defines eager-loading navigation paths for EF Core entities, ensuring related data is consistently queried and mapped across repository implementations.

Can I generate DI wiring for a new EF Core entity automatically?

Yes, DI registration for a new EF Core entity is generated automatically alongside the repository interface and implementation, wiring the data access layer into the Umbrella dependency injection container.

Do I need an existing EF Core entity to scaffold a repository?

Yes, an existing EF Core entity is required as the target input, because the scaffolding generates the interface, implementation, and IncludeMap specifically tailored to that entity's structure.

Does this scaffolding work with non-Umbrella EF Core projects?

No, this scaffolding is specifically designed for Umbrella-based projects that adopt the GenericDbRepository pattern, ensuring the generated query method skeletons and DI wiring match Umbrella's conventions.

What's the best way to onboard a new EF Core entity into a data access layer?

The best way to onboard a new EF Core entity is to run the scaffold tool, which rapidly generates the repository interface, implementation, IncludeMap, and DI registration to integrate the entity into the data access layer.