review-code-quality

To review code quality, you analyze codebases for magic numbers, DRY violations, and separation of concerns issues. This Skill explores different code modules in parallel and validates findings with evidence and counter-arguments.

Detecting DRY violations and magic numbers requires analyzing the codebase across different code modules in parallel. This approach identifies problematic function design and naming convention issues while validating findings with evidence and counter-arguments.

Deep code analysis identifies problematic function design and naming conventions by employing a parallel exploration strategy across different code modules. It validates these quality findings with evidence and counter-arguments to ensure accurate maintainability assessments.

Yes, you can use automated code analysis to check for poor separation of concerns, inconsistent error handling, and misleading naming before merging. It performs a thorough review to catch potential long-term issues and ensure adherence to best practices.

Code quality analysis requires no specific dependencies or environment setup. It operates directly on the codebase to identify maintainability issues like magic numbers and DRY violations without needing external components.

You should use a deep codebase review for refactoring when you need to catch complex maintainability issues like DRY violations and poor separation of concerns. It validates findings with counter-arguments, going beyond standard linting to ensure long-term robustness.