Skip to content
TrustedSkillsbeta
Back to all skills

Dotnet Design Pattern Review

Official
github·vlatest·backend·MIT

Official github skill covering design, code review for developing backend services and APIs.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add github/awesome-copilot --skill dotnet-design-pattern-review -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

github

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned github/awesome-copilot at 6c4d33b9cf.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
6c4d33b9cf
Manifest
skills/dotnet-design-pattern-review/SKILL.md
Scanned
0 files
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill reviews .NET code for adherence to established design patterns, helping developers identify and correct anti-patterns or suboptimal implementations. It provides actionable feedback on how to refactor code to follow best practices in software architecture.

When to use it

  • Before merging a feature branch into the main codebase to ensure clean architectural principles are followed.
  • During code reviews to catch design flaws that may impact maintainability and scalability.
  • When refactoring legacy .NET applications to modernize their structure and improve readability.
  • To educate developers on proper usage of common patterns like Dependency Injection, Repository, or Singleton.

Key capabilities

  • Identifies misuse or absence of common .NET design patterns
  • Provides suggestions for code refactoring based on best practices
  • Highlights potential performance issues tied to poor architectural choices

Example prompts

  • "Review this C# class for adherence to the Repository pattern."
  • "Check if this ASP.NET Core service follows Dependency Injection principles."
  • "Analyze this .NET application for common anti-patterns and suggest improvements."

Tips & gotchas

  • Ensure your code is well-documented, as the tool may rely on comments to understand intent.
  • This skill works best with clean, modular code; highly coupled or legacy systems may require manual intervention alongside automated feedback.