Provides atomic transaction control for .NET Clean Architecture write operations.
npx skills add https://github.com/yeeehaooo/WorkSpace --skill unit-of-work
Please help me install this Agent Skill. Skill: unit-of-work Source: https://github.com/yeeehaooo/WorkSpace/tree/main/skills/dotnet/patterns/unit-of-work Command: npx skills add https://github.com/yeeehaooo/WorkSpace --skill unit-of-work
Provide transactional boundary control for write operations in .NET Clean Architecture applications.
Configure a UnitOfWork at the start of a command handler to begin a transaction, perform repository operations, and commit or rollback as needed.
High-intent search queries and answers about installing and using this skill.
To manage transaction boundaries across multiple repositories in .NET Clean Architecture, define IUnitOfWork in the Application layer and implement it in Infrastructure to coordinate atomic multi-repository updates, exposing BeginAsync, CommitAsync, and RollbackAsync methods.
The Unit of Work pattern for coordinating atomic operations in CQRS applications provides transactional boundary control for write operations, ensuring commands that require multiple repository updates execute atomically or roll back entirely.
Yes, you can handle nested transactions in scoped dependency injection scenarios using .NET by implementing a UnitOfWork pattern that supports nested transactions, utilizing an internal IDbSession and providing automatic rollback on Dispose.
Preventing repositories from managing their own database transactions in Clean Architecture avoids anti-patterns by centralizing transactional boundary control at the command handler level, ensuring atomic operations and consistent multi-repository updates.
To implement transaction management command handlers in .NET with Dapper, configure a DapperUnitOfWork at the start of the handler to begin a transaction, perform repository operations, and commit or rollback as needed using the exposed async methods.
Yes, the Unit of Work pattern supports automatic rollback on unhandled exceptions in .NET by triggering rollback during the Dispose phase of the scoped dependency injection lifecycle, ensuring atomic multi-repository updates remain consistent.
FaysilAlshareefEnforce four-layer separation and dependency inversion in .NET projects.
JetBrainsDefine safe transaction boundaries for Kotlin and Spring workflows.
mepukaDefine service interfaces and bind live/test implementations through layers.
bobmatnycGuide Visual Basic .NET database interactions with ADO.NET and Entity Framework Core.
