code-smell-detector

To detect code smells and quantify technical debt, you need static analysis that identifies anti-patterns and SOLID violations. This skill scans JavaScript and TypeScript projects, outputting prioritized findings with severity scores, file:line references, and remediation guidance.

Finding SOLID violations and maintainability issues requires repository-wide static analysis. This skill evaluates your codebase against SOLID principles, assigning quantified severity scores to each violation and providing actionable evidence with specific file and line references for targeted refactoring.

Yes, static analysis can prioritize refactoring by scoring code quality metrics. This skill calculates severity scores for detected code smells and anti-patterns, allowing you to prioritize technical debt reduction efforts based on quantified maintainability issues and practical remediation guidance.

Code smell detection works with both JavaScript and TypeScript projects. It provides actionable evidence for identified anti-patterns and maintainability issues by outputting exact file:line references, ensuring you can quickly locate and resolve SOLID violations across your repository.

Common code smells and anti-patterns identified during static analysis include SOLID violations and various maintainability issues. This skill detects these technical debt indicators across your repository, quantifying their severity and generating prioritized findings with actionable evidence to guide code improvements.

Maintainability degrades due to accumulated code smells and anti-patterns. You measure code health by applying static analysis to quantify severity scores for technical debt, generating actionable evidence and prioritized findings that guide targeted refactoring to improve overall repository maintainability.