code-smell-audit

Audit Python and TypeScript codebases for code smells across five categories.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/TDMorales/skill_set_library --skill code-smell-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-smell-audit
Source: https://github.com/TDMorales/skill_set_library/tree/main/skills/.experimental/code-smell-audit
Command: npx skills add https://github.com/TDMorales/skill_set_library --skill code-smell-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and examples (resource) components.

What problem does it solve?

This Skill identifies code smells, which are surface-level indicators of deeper design problems, helping to improve code quality, maintainability, and reduce the risk of defects.

Core Features & Use Cases

  • Code Smell Detection: Audits code across five canonical categories (Bloaters, OO Abusers, Change Preventers, Dispensables, Couplers) to find specific smells.
  • Structured Findings: Produces detailed reports (AUDIT.md) with severity, location, evidence, and refactoring recommendations for each smell.
  • Refactoring Planning: In 'plan' mode, generates a prioritized roadmap for addressing identified smells.
  • Use Case: A development team wants to proactively improve the quality of a legacy Python codebase. They use this Skill to audit the entire repository, identify the most critical code smells, and generate a phased plan for refactoring.

Quick Start

Run a code smell audit on the current repository, focusing on Python files.

Frequently Asked Questions about code-smell-audit

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

FAQPage Schema
How do I detect code smells in a Python or TypeScript codebase?

Detect code smells by auditing your codebase across five categories: Bloaters, Object-Orientation Abusers, Change Preventers, Dispensables, and Couplers. This Skill analyzes Python, TypeScript, and mixed-language projects to pinpoint specific design flaws.

What is the best way to plan refactoring steps for legacy code?

The best way to plan refactoring is to use an audit mode that generates a prioritized remediation roadmap. It evaluates identified code smells by severity to produce a structured, phased plan for addressing deeper design problems.

Can I run a static analysis audit on specific file paths in my repository?

Yes, you can run static analysis on specific target paths within your repository. The audit allows you to specify directories or files to focus the code smell detection on the most critical areas of your project.

What specific code smell categories are evaluated during a static code audit?

A static code audit evaluates five canonical code smell categories: Bloaters, Object-Orientation Abusers, Change Preventers, Dispensables, and Couplers. This comprehensive coverage identifies surface indicators of deeper software design issues.

How does an audit report help improve software design and maintainability?

An audit report improves software design by detailing findings, severity, location, and evidence for each detected code smell. It provides specific refactoring recommendations to reduce defect risks and enhance maintainability.

Does this code smell audit support mixed-language projects?

Yes, the code smell audit fully supports mixed-language projects alongside dedicated Python and TypeScript analysis. This allows development teams to assess code quality consistently across diverse technology stacks.