gof-evaluator

Detect GoF patterns and antipatterns in code, outputting a structured analysis report with refactors.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill gof-evaluator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gof-evaluator
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/patterns/skills/gof-evaluator
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill gof-evaluator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly identify GoF patterns and antipatterns in existing codebases, enabling targeted refactoring and design improvements.

Core Features & Use Cases

  • Pattern detection: analyzes per-class/module structures to detect GoF patterns, misuses, and obsolete implementations.
  • Antipattern detection: flags anti-patterns and provides signals for remediation.
  • Guided output: produces a structured report detailing findings and suggested next steps.

Quick Start

Run an analysis on your codebase to surface GoF patterns, antipatterns, and refactoring suggestions.

Frequently Asked Questions about gof-evaluator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify GoF design patterns in my codebase?

You can identify GoF design patterns by running an automated analysis on your per-class or per-module codebase to detect correct, degraded, or obsolete pattern implementations and output a structured report.

How do I detect design pattern antipatterns during a code review?

Detect design pattern antipatterns during a code review by analyzing your code structures to flag misuses and obsolete implementations, which provides clear signals for remediation and refactoring.

What is the best way to find misused design patterns for refactoring?

The best way to find misused design patterns for refactoring is to analyze existing code at the class or module level, detecting degraded patterns and generating a structured report with suggested next steps.

Can I analyze per-module codebases to find obsolete design patterns?

Yes, you can analyze per-module codebases to find obsolete design patterns by evaluating the structural code to detect outdated implementations and outputting a detailed analysis with recommended refactors.

Why does my codebase need GoF pattern detection before refactoring?

Your codebase needs GoF pattern detection before refactoring to quickly identify correct, degraded, or obsolete patterns and antipatterns, enabling targeted design improvements and preventing architectural degradation.