clean-code

To refactor code for readability and maintainability, paste your code and request a review that identifies naming issues, oversized functions, unclear error handling, and boundary violations. This provides actionable guidance to split responsibilities and apply clean code principles.

The best way to review code for clean code violations is to analyze the pull request diff for intent-revealing names, small focused functions, explicit error handling, and clear test design. Paste the code to highlight refactoring opportunities before merging.

Yes, you can get naming guidance for variables, functions, classes, and files during a code review. Provide the code snippet to receive suggestions for intent-revealing names that improve overall readability and maintainability.

Improve unit test quality in legacy code by analyzing test design for clarity and coverage alongside the refactored code. Paste your tests to ensure they validate behavior effectively without coupling to implementation details.

Yes, this clean code review approach works for object boundaries and class structure design by evaluating dependency limits and class organization. Paste your class definitions to identify boundary violations and structural improvements.

Avoid automated refactoring suggestions for error handling when complex domain rules require explicit, custom logic that generic clean code patterns cannot interpret. Review suggested changes manually to ensure error handling remains contextually accurate.