gof-review

One-line summary

Audit code that claims to (or appears to) use GoF design patterns — checking that the pattern's intent, structure, and trade-offs are honoured, not just its name.

When to use this skill

• A pull request introduces a pattern and the reviewer wants a structured check.
• Onboarding into a codebase with *Factory, *Strategy, *Adapter, *Manager everywhere and wanting to know which are real uses and which are pattern theatre.
• The user suspects a pattern is being misapplied (over-engineered, misnamed, wrong intent).

When NOT to use this skill

• The user wants to introduce a pattern → route to gof-identify or gof-refactor-to-pattern.
• The user has a domain modeling problem, not a code-level pattern question → route to ddd-review or ddd-design.

Core content

Review the target file or module against this catalog of pattern misuses. For each finding, report severity (blocker / major / minor), location, and the pattern skill that explains the fix.