refactor

Topics in the source

• Refactor
• Overview
• When to Use
• Refactoring Principles
• The Golden Rules
• When NOT to Refactor
• Common Code Smells & Fixes
• 1. Long Method/Function

Improve code structure and readability without changing external behavior. Refactoring is gradual evolution, not revolution. Use this for improving existing code, not rewriting from scratch. Use this skill when: Code is hard to understand or maintain Functions/classes are too large Code smells need addressing Adding features is difficult due to code structure User asks "clean up this code", "refactor this", "improve this" -- 1. Behavior is preserved - Refactoring doesn't change what the code does, only how 2. Small steps - Make tiny changes, test after each 3. Version control is your friend - Commit before and after each safe state 4. Tests are essential - Without tests, you're not refactoring, you're editing 5. One thing at a time - Don't mix refactoring with feature changes -- -- -- -- -- -- [ ] Functions are small (< 50 lines) [ ] Functions do one thing [ ] No duplicated code [ ] Descriptive names (variables, functions, classes) [ ] No magic numbers/strings [ ] Dead code removed [ ] Related code is together [ ] Clear module boundaries [ ] Dependencies flow in one direction [ ] No circular dependencies [ ] Types defined for all public APIs [ ] No any types without justification [

This is an excerpt. Refer to the complete source and its current requirements.