refactoring-assistant

Detect code smells and guide incremental refactoring of legacy codebases.

2|2|Updated Jan 16, 2026

Search Tags:#refactor #code-quality #solid #software-design #code-smells #technical-debt #dry

Ready to run

npx skills add https://github.com/mehdiozdemir/awesome-agent-skills --skill refactoring-assistant-mehdiozdemir

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: refactoring-assistant
Source: https://github.com/mehdiozdemir/awesome-agent-skills/tree/main/skills/refactoring-assistant
Command: npx skills add https://github.com/mehdiozdemir/awesome-agent-skills --skill refactoring-assistant-mehdiozdemir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refactoring helps transform messy, high-complexity code into clean, maintainable architectures by systematically addressing code smells and architecture defects.

Core Features & Use Cases

Systematic detection of code smells and architecture issues to guide targeted refactoring.
Application of SOLID, DRY, KISS, and YAGNI principles to improve structure and readability.
Incremental, test-driven refactoring plans that reduce risk and preserve behavior.

Quick Start

Analyze a legacy module and propose an incremental refactoring plan to improve readability and maintainability.

Frequently Asked Questions about refactoring-assistant

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

FAQPage Schema

How do I identify code smells in a legacy codebase?▼

Code smells in a legacy codebase are identified through systematic detection of structural defects and architecture issues. This process guides targeted refactoring strategies to improve maintainability while preserving existing behavior.

What is the best way to refactor legacy code without breaking existing functionality?▼

The best way to refactor legacy code safely is through incremental, test-driven refactoring plans. This approach reduces risk by validating behavior through tests at each step while improving structure and readability.

How do SOLID, DRY, and KISS principles apply to software refactoring?▼

SOLID, DRY, and KISS principles guide software refactoring by providing patterns to resolve code smells and architecture defects. They systematically transform high-complexity code into clean, maintainable structures.

Can I use incremental refactoring to reduce technical debt across multiple modules?▼

Incremental refactoring reduces technical debt across multiple modules by applying targeted strategies and updating documentation. This repeatable workflow detects smells, validates behavior through tests, and ensures measurable maintainability improvements.

When should I not attempt to refactor complex legacy code?▼

You should not refactor complex legacy code without a test-driven safeguard in place. Without tests to validate behavior, incremental refactoring risks breaking existing functionality and increasing technical debt rather than reducing it.