code-smell-doctor

Analyze code for 23 classic code smells and provide refactoring recommendations.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/twiced-technology-gmbh/seedr --skill code-smell-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-smell-doctor
Source: https://github.com/twiced-technology-gmbh/seedr/tree/main/.claude/skills/code-smell-doctor
Command: npx skills add https://github.com/twiced-technology-gmbh/seedr --skill code-smell-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and rectify common code smells and anti-patterns that degrade software quality, maintainability, and readability.

Core Features & Use Cases

  • Comprehensive Smell Detection: Analyzes code for 23 classic code smells across five categories (Bloaters, OO Abusers, Change Preventers, Dispensables, Couplers).
  • Actionable Recommendations: Provides specific refactoring techniques and severity ratings for each detected smell.
  • Use Case: When a developer is asked to "review code quality" or "refactor a complex module," this Skill can systematically audit the codebase for potential issues and suggest improvements.

Quick Start

Analyze the provided code snippet for any code smells and suggest refactoring opportunities.

Frequently Asked Questions about code-smell-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify code smells in a complex module?

Detect technical debt by auditing your codebase for 23 classic code smells across categories like Bloaters, Change Preventers, and Dispensables. The analysis provides specific refactoring recommendations and severity ratings to systematically resolve maintainability issues.

What is the best way to audit code quality for technical debt?

The best way to audit code quality is to analyze the source code against 23 classic code smell anti-patterns. This approach identifies technical debt across five categories—such as Object-Orientation Abusers and Couplers—and provides actionable refactoring techniques to fix them.

How do I find refactoring opportunities when reviewing software design?

Find refactoring opportunities by analyzing code for anti-patterns that degrade software design, such as Change Preventers and Dispensables. The analysis detects specific code smells and suggests targeted refactoring techniques to improve overall readability and design structure.

Does this code smell detection work with any programming language?

Code smell detection analyzes provided code snippets for 23 classic structural anti-patterns across five categories, including Object-Orientation Abusers and Couplers. It evaluates software design principles conceptually, making it applicable for auditing code quality across various programming languages.

What types of code smells are covered during a maintainability audit?

A maintainability audit covers 23 classic code smells across five categories: Bloaters, Object-Orientation Abusers, Change Preventers, Dispensables, and Couplers. Each detected issue includes a severity rating and specific refactoring recommendations to improve software quality.