Mindset
Apply this skill whenever you need an objective assessment of code quality. ALWAYS look beyond surface-level issues. NEVER ignore structural concerns in favor of style-only feedback.
When to Use
- Reviewing code for quality improvements
- Assessing technical debt levels
- Onboarding new developers to quality standards
Procedures
- Analyze the code structure for cohesion and coupling
- Check naming conventions and readability
- Identify duplicated logic and refactoring opportunities
- Score overall quality and list top improvements
Anti-Patterns
BAD: Focusing only on formatting
# BAD — formatting is surface-level; structural issues matter more
black my_module.py
GOOD: Evaluate logical structure, responsibilities, and abstractions first.