codeprobe-patterns

Identify design-pattern opportunities and anti-patterns during code reviews by auditing multi-language codebases to detect where patterns like Strategy or State would improve clarity, and flagging God classes or unnecessary indirection that add complexity.

Common anti-patterns to look for when refactoring architecture include God classes and unnecessary indirection that add abstraction without benefit, complicating maintenance tasks across the codebase and reducing overall clarity and flexibility.

You can detect GoF pattern opportunities in a multi-language codebase by running a pattern auditor that analyzes repositories to surface prioritized recommendations for applying patterns like Strategy, State, or Facade to reduce complexity.

Generate actionable fix prompts for design pattern misuse by detecting instances where a named pattern would improve clarity or flexibility, then outputting concrete prompts with pattern names, goals, and implementation sketches to guide refactoring.

You should not use a design pattern during maintenance tasks when it introduces unnecessary indirection without benefit, as pattern misuse adds abstraction layers that complicate the codebase and make ongoing maintenance harder rather than improving flexibility.