PluginBench
Skill
Official
Review
Audit score 70

dotnet-design-pattern-review

github/awesome-copilot

Review C#/.NET code for design pattern implementation and architectural improvements.

What is dotnet-design-pattern-review?

Analyzes C#/.NET code against established design patterns (Command, Factory, Dependency Injection, Repository, Provider, Resource) and SOLID principles. Provides actionable recommendations for pattern adoption, architecture consistency, and .NET best practices without modifying code.

  • Identifies design patterns used and detects missing beneficial patterns
  • Evaluates SOLID principle compliance and architectural violations
  • Checks .NET best practices including primary constructors, async/await, and ResourceManager usage
  • Assesses separation of concerns, namespace conventions, and modular structure
  • Reviews testability, security, and performance considerations
  • Validates GoF pattern implementations (Command, Factory, Template Method, Strategy)

How to install dotnet-design-pattern-review

npx skills add https://github.com/github/awesome-copilot --skill dotnet-design-pattern-review
Claude Code
Cursor
Windsurf
Cline

How to use dotnet-design-pattern-review

  1. 1.Select the C#/.NET code or project folder you want reviewed
  2. 2.Run the skill to analyze design pattern implementation
  3. 3.Review the generated recommendations for pattern usage and improvements
  4. 4.Check the improvement focus areas for Command Handlers, Factories, Providers, and Configuration
  5. 5.Apply suggested changes to align with .NET best practices and SOLID principles

Use cases

Good for
  • Review a new microservice for design pattern consistency before merging
  • Audit legacy .NET codebase for SOLID principle violations and refactoring opportunities
  • Evaluate dependency injection and service provider configuration in a Console or ASP.NET application
  • Assess Command Handler implementations for proper validation and error handling
  • Check Repository and Provider pattern abstractions for async data access
Who it's for
  • C#/.NET developers reviewing code quality
  • Architects evaluating design pattern adoption
  • Teams migrating to modern .NET practices
  • Code reviewers checking SOLID compliance
  • Developers building command-driven or provider-based applications

dotnet-design-pattern-review FAQ

Does this skill modify my code?

No. This skill provides a review and recommendations only. It does not make any changes to your code.

What design patterns does it check for?

It evaluates Command Pattern, Factory Pattern, Dependency Injection, Repository Pattern, Provider Pattern, and Resource Pattern implementations.

Does it check SOLID principles?

Yes. It reviews Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion principles.

Can it review ASP.NET and Console applications?

Yes. It works with any C#/.NET project structure, including Console, ASP.NET, and service-based applications.

What output should I expect?

Specific, actionable recommendations aligned with your project's architecture, including pattern improvements, best practice violations, and refactoring suggestions.

Full instructions (SKILL.md)

Source of truth, from github/awesome-copilot.


name: dotnet-design-pattern-review description: 'Review the C#/.NET code for design pattern implementation and suggest improvements.'

.NET/C# Design Pattern Review

Review the C#/.NET code in ${selection} for design pattern implementation and suggest improvements for the solution/project. Do not make any changes to the code, just provide a review.

Required Design Patterns

  • Command Pattern: Generic base classes (CommandHandler<TOptions>), ICommandHandler<TOptions> interface, CommandHandlerOptions inheritance, static SetupCommand(IHost host) methods
  • Factory Pattern: Complex object creation service provider integration
  • Dependency Injection: Primary constructor syntax, ArgumentNullException null checks, interface abstractions, proper service lifetimes
  • Repository Pattern: Async data access interfaces provider abstractions for connections
  • Provider Pattern: External service abstractions (database, AI), clear contracts, configuration handling
  • Resource Pattern: ResourceManager for localized messages, separate .resx files (LogMessages, ErrorMessages)

Review Checklist

  • Design Patterns: Identify patterns used. Are Command Handler, Factory, Provider, and Repository patterns correctly implemented? Missing beneficial patterns?
  • Architecture: Follow namespace conventions ({Core|Console|App|Service}.{Feature})? Proper separation between Core/Console projects? Modular and readable?
  • .NET Best Practices: Primary constructors, async/await with Task returns, ResourceManager usage, structured logging, strongly-typed configuration?
  • GoF Patterns: Command, Factory, Template Method, Strategy patterns correctly implemented?
  • SOLID Principles: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion violations?
  • Performance: Proper async/await, resource disposal, ConfigureAwait(false), parallel processing opportunities?
  • Maintainability: Clear separation of concerns, consistent error handling, proper configuration usage?
  • Testability: Dependencies abstracted via interfaces, mockable components, async testability, AAA pattern compatibility?
  • Security: Input validation, secure credential handling, parameterized queries, safe exception handling?
  • Documentation: XML docs for public APIs, parameter/return descriptions, resource file organization?
  • Code Clarity: Meaningful names reflecting domain concepts, clear intent through patterns, self-explanatory structure?
  • Clean Code: Consistent style, appropriate method/class size, minimal complexity, eliminated duplication?

Improvement Focus Areas

  • Command Handlers: Validation in base class, consistent error handling, proper resource management
  • Factories: Dependency configuration, service provider integration, disposal patterns
  • Providers: Connection management, async patterns, exception handling and logging
  • Configuration: Data annotations, validation attributes, secure sensitive value handling
  • AI/ML Integration: Semantic Kernel patterns, structured output handling, model configuration

Provide specific, actionable recommendations for improvements aligned with the project's architecture and .NET best practices.