refactoring-analysis

Analyze codebases for code smells and generate prioritized refactoring reports.

Updated Apr 2, 2026

Search Tags:#refactoring #software-quality #code-analysis #code-smells #technical-debt

Ready to run

npx skills add https://github.com/rhuangabrielsantos/skills --skill refactoring-analysis-rhuangabrielsantos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: refactoring-analysis
Source: https://github.com/rhuangabrielsantos/skills/tree/main/skills/refactoring-analysis
Command: npx skills add https://github.com/rhuangabrielsantos/skills --skill refactoring-analysis-rhuangabrielsantos

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It helps developers locate hidden design flaws, duplicated logic, and high‑coupling areas in a codebase, turning vague technical debt concerns into a clear, actionable refactoring plan.

Core Features & Use Cases

Comprehensive smell detection across bloated functions, duplicated code, coupling, and more, based on Martin Fowler’s catalog.
Prioritized refactoring report saved automatically to the docs/_refacs folder for immediate team consumption.
Flexible scope: analyze an entire repository, a specific module, or a feature area, with optional SOLID analysis for domain‑driven projects.

Quick Start

Ask the refactoring-analysis skill to analyze the src folder of your project and generate a refactoring report.

Frequently Asked Questions about refactoring-analysis

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

FAQPage Schema

How do I identify code smells and refactoring opportunities in my codebase?▼

Code smell detection scans specified directories for bloated functions, duplicated code, and high coupling. This process identifies structural issues based on Martin Fowler’s catalog, turning vague technical debt concerns into a clear, prioritized refactoring report.

Can I analyze technical debt in a specific module instead of the whole repository?▼

You can analyze technical debt across flexible scopes, targeting an entire repository, a specific module, or a feature area. This generates a prioritized refactoring report saved to the docs folder, isolating structural issues for immediate team consumption.

What is the best way to prioritize refactoring tasks for domain-driven designs?▼

Prioritizing refactoring tasks for domain-driven designs involves applying optional SOLID analysis alongside standard code smell detection. This evaluates structural issues and coupling to produce a prioritized report tailored to your domain logic.

Does code smell detection work with any programming language or paradigm?▼

Code smell detection works across any language or paradigm. It scans your specified directory to locate duplicated logic, high coupling, and structural issues, ensuring comprehensive smell detection regardless of your tech stack.

How do I generate a refactoring report for my development team?▼

You generate a refactoring report by analyzing your source folder for structural issues. The report is saved automatically to the docs/_refacs folder, providing an actionable refactoring plan for immediate team consumption.

When should I not use automated refactoring analysis for technical debt?▼

Automated refactoring analysis may not be suitable for highly dynamic or runtime-dependent logic where structural issues are not easily detectable through static directory scanning. It focuses on code smells, duplicated code, and coupling.