How to implement the Repository and Unit of Work patterns with EF Core? (Pros/Cons)

While historically popular, implementing custom Repository/Unit of Work patterns over EF Core is highly debated because DbSet and DbContext already implement them.

A generic repository wraps DbSet, and Unit of Work wraps SaveChanges(). Pros: Can mock DB access easily for unit testing, centralizes custom business-data logic, and isolates the application from EF Core APIs. Cons: Massive boilerplate, hides powerful EF Core features (like Split Queries or Projection), and DbContext already is a Unit of Work.