Skills

Skill 142 of 200

.NET Design Pattern Review

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

1 minute · 322 words · 4 sections

Install

$ npx skills add github/awesome-copilot --skill dotnet-design-pattern-review

$ npx skills add github/awesome-copilot

» /plugin marketplace add github/awesome-copilot

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

.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.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/github/awesome-copilot, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .github/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

3 of 200 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 295°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “4 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .github/plugin/marketplace.json by GitHub, declaring 162 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /github/awesome-copilot.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

.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.