design-principle-enforcer

You can enforce SOLID principles during a code review by applying an adversarial critique approach that evaluates class design, coupling, and misplaced responsibilities, demanding justification for deviations rather than simply approving the code.

The best way to check separation of concerns before opening a PR is to review your feature branch and verify that business logic is fully separated from UI, data access, and routing components across your codebase.

Yes, design principle enforcement applies across languages and frameworks because it evaluates universal architecture concepts like class design, coupling, and separation of concerns rather than relying on language-specific syntax rules.

To refactor spaghetti code to align with SOLID architecture, review the codebase to identify misplaced responsibilities and missing abstractions, then follow guided refactor suggestions that restructure class design without directly implementing the code changes.

Your code review may fail to prevent spaghetti code if it skips adversarial critiques of class design and separation of concerns, allowing clever implementations and tightly coupled business logic to pass without demanding justification.