code-quality-rules

To eliminate code duplication during a code review, enforce DRY principles by identifying repeated validation logic across endpoints and extracting the shared validators into a central, reusable module. This process targets redundant logic and parallel inheritance hierarchies to improve maintainability.

The best way to decompose large files and classes is to break them down into single-responsibility components aligned with SOLID principles and domain-driven design boundaries. This structural decomposition prevents shotgun surgery across modules and makes codebases easier to debug and extend.

To extract magic numbers and configuration values, identify hardcoded values scattered throughout the codebase and move them into centralized, reusable locations. Standardized extraction patterns for constants, shared utilities, and configuration values ensure consistent code quality.

Yes, you can apply these code refactoring rules to general-purpose programming languages. The rules enforce DRY principles, SOLID-aligned single-responsibility decomposition, and standardized extraction patterns without relying on language-specific dependencies.

Poor structural decomposition makes codebases hard to maintain because it leads to inconsistent code quality, unnecessary duplication, and scattered logic. This structural design decay forces shotgun surgery across modules whenever features are added or modified.