work_coding_refactor-guide

Detect code smells and propose incremental, validated refactoring across JavaScript, Python, and Java projects.

1|Updated Apr 16, 2026

Search Tags:#refactor #rename #incremental #code-smells #code-cleanup #extract-function

Ready to run

npx skills add https://github.com/JoNaYeon/claude-code-skills --skill work-coding-refactor-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work_coding_refactor-guide
Source: https://github.com/JoNaYeon/claude-code-skills/tree/main/work/coding/work_coding_refactor-guide
Command: npx skills add https://github.com/JoNaYeon/claude-code-skills --skill work-coding-refactor-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and resolves code smells to prevent technical debt, enabling teams to improve readability, reduce duplication, and simplify future changes.

Core Features & Use Cases

Detect common code smells (long methods, large classes, duplicated logic) and prioritize fixes.
Propose safe, incremental refactor steps (extract function, rename identifiers, move code, simplify conditionals) with rationale.
Apply changes in small, verifiable steps and document before/after state for traceability.

Quick Start

Provide a concise plan to refactor a given function or module and implement one safe, incremental change.

Frequently Asked Questions about work_coding_refactor-guide

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

FAQPage Schema

How do I refactor long methods and duplicated logic in a multi-file project?▼

Identify code smells like long methods and large classes, then resolve them through structured refactoring planning. The process proposes safe, incremental steps such as extracting functions and simplifying conditionals to reduce technical debt.

What is the best way to plan incremental code cleanup without breaking existing functionality?▼

The best way to plan incremental code cleanup is to apply changes in small, verifiable steps and validate them with tests. This approach documents the before and after state for traceability while ensuring existing functionality remains intact.

Can I use this refactoring approach across different programming languages like JavaScript, Python, and Java?▼

Yes, this refactoring approach applies to multi-file projects across languages like JavaScript, Python, and Java. It provides a language-agnostic framework to detect smells, rename identifiers, and simplify conditionals safely.

How do I identify and prioritize which code smells to fix first?▼

Identify and prioritize code smells by detecting common issues such as long methods, large classes, and duplicated logic. The framework evaluates these smells and proposes structured fixes to prevent technical debt from accumulating.

Why should I document the before and after state when renaming identifiers and extracting functions?▼

Documenting the before and after state when renaming identifiers and extracting functions ensures traceability for your incremental changes. It provides clear rationale for each refactoring step, enabling teams to simplify future changes safely.