clean-code

To enforce clean coding standards during code review, check for anti-patterns like magic numbers, feature envy, or excessive function arguments, then apply refactoring heuristics to improve readability and maintainability.

Intention-revealing names and function design require writing small functions that do one thing at a single level of abstraction, ensuring code structure remains orderly and readable.

Refactoring a legacy system to reduce technical debt involves enforcing clean coding standards, applying SOLID design principles, and improving class cohesion through the single responsibility principle.

Yes, the clean code framework provides quality assurance checklists for error handling and unit testing based on the F.I.R.S.T. principles to ensure software testability and code quality.

The best way to analyze a module for single responsibility principle violations is to use a clean code skill to detect naming inconsistencies and poor class cohesion, then apply structured refactoring heuristics.

Apply SOLID design principles during new feature development whenever requirements for readability, testability, and maintainability must be satisfied to prevent accumulating technical debt.