clean-code

To refactor messy code into clear, maintainable functions, you decompose oversized logic by extracting methods, applying intention-revealing names, and enforcing single responsibility. This reduces technical debt and makes future changes safer and easier to read.

Common code smells include duplicated logic, unclear names, oversized functions, and fragile classes. You fix code smells by performing extract-method refactors, renaming identifiers for clarity, and applying SOLID principles to separate responsibilities.

You use TDD workflows to safely improve code readability by writing tests first to protect the refactor, then suggesting minimal, test-backed changes. This ensures your intention-revealing names and extract-method refactors do not break existing behavior.

You should not apply heavy-handed design patterns during a code review when the goal is strictly readability and maintainability. Avoid performance- or architecture-level prescriptions, and focus instead on minimal moves like naming improvements and function decomposition.

Yes, you can review and refactor source code across mixed-language codebases. The guidance applies to small to medium codebases, handling mixed-language examples by targeting intention-revealing names, abstraction levels, and error handling.