OO Design Smell Detector

When to Use

You are auditing an object-oriented codebase — or a specific class or subsystem within one — for structural design problems that make change expensive. Typical triggers:

• "Every time I add a feature, I have to change 10 files"
• "This class hierarchy is getting out of control"
• "Changing the database means rewriting half the codebase"
• "I can't swap out this algorithm without touching everything that calls it"
• "We need to extend this library class but can't modify it"
• "New platforms require total rewrites"
• A pre-refactoring audit before a redesign sprint
• A code review specifically targeting design quality, not just style

Before starting, verify:

• Is there a specific class, subsystem, or entire codebase to scan?
• Is the user looking for an exhaustive audit or a targeted check on one smell category?