Source profileQuality 72/100

github/awesome-copilot/skills/dotnet-design-pattern-review/SKILL.md

dotnet-design-pattern-review

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

Source repository stars
37,126
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/github/awesome-copilot --skill "skills/dotnet-design-pattern-review"
    Safe inspection promptEditorial

    Inspect the Agent Skill "dotnet-design-pattern-review" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/dotnet-design-pattern-review/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Review Checklist

      Design Patterns: Identify patterns used. Are Command Handler, Factory, Provider, and Repository patterns correctly implemented? Missing beneficial patterns?

      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?
    2. 02

      Required Design Patterns

      Command Pattern: Generic base classes (CommandHandler), ICommandHandler interface, CommandHandlerOptions inheritance, static SetupCommand(IHost host) methods

      Command Pattern: Generic base classes (CommandHandler), ICommandHandler interface, CommandHandlerOptions inheritance, static SetupCommand(IHost host) methodsFactory Pattern: Complex object creation service provider integrationDependency Injection: Primary constructor syntax, ArgumentNullException null checks, interface abstractions, proper service lifetimes
    3. 03

      Improvement Focus Areas

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

      Command Handlers: Validation in base class, consistent error handling, proper resource managementFactories: Dependency configuration, service provider integration, disposal patternsProviders: Connection management, async patterns, exception handling and logging

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score72/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars37,126SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    github/awesome-copilot
    Skill path
    skills/dotnet-design-pattern-review/SKILL.md
    Commit
    9933dcad5be5caeb288cebcd370eeeb2fc2f1685
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

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

    Alternatives

    Compare before choosing

    Computed 10042,015

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    2026-07-270 platforms
    Computed 1007

    event4u-app/agent-config

    design-intelligence

    Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

    2026-07-280 platforms
    Computed 1007

    event4u-app/agent-config

    existing-ui-audit

    Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.

    2026-07-280 platforms
    Computed 9982,073

    nexu-io/open-design

    emil-design-eng

    This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

    2026-07-280 platforms