klod68/gen-repository

name: gen-repository description: "Use when adding a new repository to a feature. Generates an IRepository interface and EF Core implementation with AsNoTracking read methods, write methods, and unit/integration test stubs. Also invoke when the user mentions: new repository, add data access, EF repository, create repository class. Domain: Code Generation, Data Access. Level: Intermediate."

Generate a repository for entity: ${1:EntityName}.

Context

• Namespace root: ${2:MyApp}
• EF DbContext class: ${3:AppDbContext}
• Operations needed: ${4|GetById,GetAll,Add,Update,Delete,GetById+GetAll,GetById+Add+Update+Delete,Full CRUD|}
• Returns paged results: ${5|Yes,No|}

Required output — generate ALL of the following:

1. Repository interface (Domain layer)

${2}.Domain.Repositories.I${1}Repository.cs

• All methods async, returning Task<T>.
• All methods accept CancellationToken cancellationToken.
• Method naming follows CQS: GetByIdAsync, FindAllAsync, AddAsync, DeleteAsync.
• Returns domain interfaces or value types — never IQueryable<T>.
• If paged: returns PagedResult<T> (define the record here if not already present).

2. EF Core implementation (Infrastructure layer)

${2}.Infrastructure.Repositories.${1}Repository.cs

• internal sealed class implementing I${1}Repository.
• Injected: ${3} via constructor.
• All read queries use AsNoTracking().
• Projects to DTO/domain type with Select() at query level — never maps full entities in memory.
• No raw SQL unless specified; if used, add an inline comment explaining why LINQ was insufficient.

3. DI registration snippet

Show the IServiceCollection extension line to register I${1}Repository → ${1}Repository as Scoped.

4. Unit test class (mock DbContext)

${2}.Infrastructure.Tests.Repositories.${1}RepositoryTests.cs

• xUnit, FluentAssertions, Moq (or EF Core in-memory provider if appropriate).
• Cover: found, not found, null argument, cancellation propagated.
• Arrange-Act-Assert with comments.

Rules

• Repository interfaces live in the Domain or Application layer — never in Infrastructure.
• Implementations are internal sealed in the Infrastructure layer.
• All read methods use AsNoTracking() — no exceptions.
• Project to DTOs with Select() at query level — never load full entities then map in memory.
• Never return IQueryable<T> from a repository — always materialize results.
• SaveChangesAsync is never called inside the repository — that is the handler's responsibility.
• Method naming follows CQS: GetByIdAsync (query), AddAsync (command), DeleteAsync (command).

Constraints

• Follow all rules in the workspace root instruction file and ef-core.instructions.md.
• internal sealed on the implementation class.
• I${1}Repository is public (it is a domain interface).
• DbContext never crosses the Infrastructure boundary.