agentsclimarketplace
Sign in

Design pattern implementation

Skill JeremyMorgan/code-review-skills/skills/design-pattern-implementation

Reviews how design patterns are used or misused across the codebase and where patterns would help. Use when evaluating architecture, pattern fit, or over-engineering.From its SKILL.md

Install
npx -y skills add JeremyMorgan/code-review-skills --skill design-pattern-implementation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as CC0-1.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, as published. Nobody here has run it

Target: $ARGUMENTS

If no target path is given above, review the entire codebase.

Review the codebase for design pattern usage.

Identify and evaluate:

  1. CREATIONAL PATTERNS

    • Singleton usage (database connections, logger)
    • Factory pattern (object creation)
    • Builder pattern (complex object construction)
    • Are they implemented correctly?

  2. STRUCTURAL PATTERNS

    • Adapter pattern (third-party integrations)
    • Facade pattern (simplified interfaces)
    • Decorator pattern (middleware)
    • Proxy pattern (caching, lazy loading)

  3. BEHAVIORAL PATTERNS

    • Strategy pattern (payment processing, auth methods)
    • Observer pattern (event handling)
    • Chain of responsibility (middleware chain)
    • Command pattern (task queuing)

  4. DOMAIN PATTERNS

    • Repository pattern (data access)
    • Service layer pattern
    • DTO/Value objects
    • Domain model pattern

For each pattern found:

  • Is it appropriate for the use case?
  • Is it implemented correctly?
  • Could a simpler solution work?
  • Are there missing patterns that would improve the code?

Recommend pattern improvements with code examples.

Provide:

A structured finding report

A scale of 1/10 on how important each finding is

Remediation: precise code-level fix or config change (snippets welcome) if possible

Constraints & style:

Be concrete and cite exact code locations and identifiers.

Prefer minimal, drop-in fix snippets over prose.

Do not invent files or functions that aren’t present; if context is missing, mark as Unable to verify and say what code would prove it.

Write this into a markdown file and place it in the audits/ folder.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.