refactoring

What problem does it solve?

This Skill addresses technical debt by systematically improving code structure, readability, and maintainability without altering any existing behavior. It adheres strictly to "Tidy First" principles, ensuring a healthier codebase for future development and reducing the risk of introducing new bugs.

Core Features & Use Cases

• Tidy First Principles: Strictly ensures that all refactoring efforts are structural improvements only; no behavioral changes are introduced, and all tests must remain green throughout the process.
• Focused Structural Improvements: Concentrates on key areas like naming clarity, duplication removal, extracting methods/classes, and reorganizing files, directly addressing common code smells.
• Incremental & Validated Changes: Promotes small, frequent changes with continuous test validation after each step, minimizing risk and simplifying debugging.
• [STRUCTURAL] Commits: Enforces clear commit messages prefixed with [STRUCTURAL], making it obvious that the changes are solely for code quality and not new features or bug fixes.
• Use Case: You've identified a "God Class" that handles too many responsibilities within your application, making it difficult to understand and modify. Activate this Skill to methodically extract smaller, more focused classes and functions, rename ambiguous variables, and reorganize the file structure, all while ensuring continuous test validation guarantees that the application's functionality remains perfectly intact.

Quick Start

Refactor the UserProcessor class in src/users/processor.js. Identify opportunities to extract methods, improve naming, and remove duplication without altering its external behavior.