dotnet-repository-async

Convert synchronous .NET data repositories to async with parameterized queries and cancellation tokens.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MauricioZwenger/ia-context --skill dotnet-repository-async
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-repository-async
Source: https://github.com/MauricioZwenger/ia-context/tree/main/skills/dotnet-repository-async
Command: npx skills add https://github.com/MauricioZwenger/ia-context --skill dotnet-repository-async

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates converting existing synchronous .NET repositories into fully asynchronous, modern, and secure codebases, improving performance and scalability.

Core Features & Use Cases

  • Refactoring legacy code: Modernize synchronous data access layers to use async/await patterns with proper cancellation support.
  • Creating new async repositories: Scaffold new data access layers adhering to best practices, including parameterized SQL and async methods.
  • Use Case: Developers updating an old monolithic .NET project can refactor data repositories to improve responsiveness and handle higher concurrency with minimal effort.

Quick Start

Use the dotnet-repository-async skill to refactor an existing C# repository with synchronous methods to include asynchronous patterns following modern standards.

Frequently Asked Questions about dotnet-repository-async

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

FAQPage Schema
How do I refactor synchronous .NET repositories to use async await?

Refactor synchronous .NET repositories to async by converting data access methods to use async/await patterns, ensuring proper cancellation token propagation and parameterized SQL queries for secure, high-performance database operations.

What is the best way to add cancellation tokens to existing C# Dapper repository methods?

Add cancellation tokens to C# Dapper repositories by passing CancellationToken parameters through async method signatures, enabling cooperative cancellation for long-running database queries and improving application responsiveness under high concurrency.

Can I scaffold new async repositories with parameterized SQL for SQL Server using Dapper?

Scaffold new async repositories with parameterized SQL for SQL Server using Dapper by generating data access layers that adhere to modern async/await standards, ensuring secure query execution and proper cancellation token handling.

Do I need C# 12 knowledge to modernize legacy .NET data access layers?

Yes, C# 12 knowledge is required to modernize legacy .NET data access layers, as the refactoring process leverages modern C# features, Dapper ORM integration, and SQL Server best practices to achieve fully asynchronous and secure codebases.

Why convert synchronous data access code to asynchronous patterns in a monolithic .NET project?

Convert synchronous data access code to asynchronous patterns in monolithic .NET projects to improve responsiveness, handle higher concurrency, and scale efficiently with minimal effort during legacy codebase modernization.