Code Smell Detector FAQs

Question 1

What types of code smells can this skill detect?

Accepted Answer

It detects five major categories: Bloaters (long methods/classes), Object-Orientation Abusers (switch statements on type), Change Preventers (shotgun surgery), Dispensables (dead code/duplicates), and Couplers (feature envy).

Question 2

Does it work with specific programming languages?

Accepted Answer

Yes, while the skill includes specific detection commands for TypeScript, JavaScript, and Python, the underlying patterns and logic are applicable to most object-oriented and functional languages.

Question 3

How do I trigger a full analysis?

Accepted Answer

You can ask Claude to 'Analyze this codebase for code smells with severity scoring' and it will use the skill's defined thresholds to scan your files.

Question 4

Can this skill help with SOLID principle compliance?

Accepted Answer

Absolutely. It specifically looks for violations like Divergent Change (Single Responsibility Principle) and Refused Bequest (Liskov Substitution Principle) to help improve your architecture.

Question 5

How does the severity scoring system work?

Accepted Answer

The skill applies specific multipliers based on the impact of the smell. For example, 'Bloaters' and 'Change Preventers' carry a 1.5x multiplier because they significantly increase cognitive load and the risk of ripple effects during changes.

Code Smell Detector

About

Key Features

Use Cases

Code Smell Detector

About

Key Features

Use Cases