dotnet-best-practices

Enforce .NET/C# best practices across solutions and generate violation reports.

Updated Mar 18, 2026

Search Tags:#csharp #dotnet #code-quality #best-practices #design-patterns #dependency-injection

Ready to run

npx skills add https://github.com/angryconsultant/Copilot-CLI --skill dotnet-best-practices-angryconsultant

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-best-practices
Source: https://github.com/angryconsultant/Copilot-CLI/tree/main/skills/dotnet-best-practices
Command: npx skills add https://github.com/angryconsultant/Copilot-CLI --skill dotnet-best-practices-angryconsultant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure .NET/C# code meets established best practices for maintainable, scalable solutions across projects.

Core Features & Use Cases

XML documentation standards for public APIs and classes
Consistent namespace structure and design patterns
Dependency Injection, Resource Localization, Async/Await, Testing, and security considerations
Guidance for architecture, logging, configuration, and code quality

Quick Start

Run a targeted code review to apply the listed best practices to the current solution and generate a report of violations

Frequently Asked Questions about dotnet-best-practices

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

FAQPage Schema

How do I enforce C# best practices across a large .NET solution?▼

To enforce C# best practices across a .NET solution, run a targeted code review to evaluate documentation, dependency injection, async patterns, and SOLID principles, generating a report of violations for the entire codebase.

What are the essential .NET code quality standards for maintainable applications?▼

Essential .NET code quality standards include XML documentation for public APIs, consistent namespace structures, proper dependency injection, async/await usage, comprehensive testing, and adherence to SOLID principles for scalable solutions.

Can I use this .NET code review guidance for Console and Service projects?▼

Yes, this .NET code review guidance applies to Console, App, Core, and Service projects of varying sizes, ensuring architecture, configuration, error handling, and security considerations are consistently met across different project types.

What's the best way to check dependency injection and async patterns in C#?▼

The best way to check dependency injection and async patterns in C# is to evaluate the codebase against industry-standard best practices, identifying violations in resource management and async/await usage to improve overall code quality.

Does this tool provide guidance for Semantic Kernel integration in .NET?▼

Yes, this tool provides specific guidance for Semantic Kernel integration in .NET, ensuring AI integration meets established code quality, error handling, and configuration standards within your solution.

When do I need to review XML documentation and namespace structure in .NET?▼

You need to review XML documentation and namespace structure in .NET when establishing maintainable, scalable solutions, ensuring public APIs and classes meet consistent design patterns and documentation standards across the project.