expert-code-quality

Detect code smells in Java codebases and recommend refactorings with design patterns.

13|3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill expert-code-quality
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expert-code-quality
Source: https://github.com/wonderslife/pdd-skills-v3/tree/main/skills/entropy/expert-code-quality
Command: npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill expert-code-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineering teams systematically improve code quality by detecting code smells and guiding targeted refactoring and design-pattern applications to create cleaner, more maintainable systems.

Core Features & Use Cases

  • Code smell detection guided by Fowler's catalog (method-level, class-level, and relationship smells) and practical checklists.
  • Comprehensive refactoring techniques and GoF design patterns with concrete transformation guidance and trade-offs.
  • Integrated workflow from sniffing issues to planning, implementing, and validating improvements, including collaboration with other skills like testing and review.

Quick Start

Inspect a Java project, identify prominent smells, and propose precise refactorings and pattern recommendations with actionable steps.

Frequently Asked Questions about expert-code-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify code smells in a Java codebase to improve maintainability?▼

Code smell detection in Java uses Fowler's catalog to analyze method-level, class-level, and relationship smells, yielding a targeted list of maintainability issues for systematic refactoring.

What's the best way to apply SOLID principles and design patterns during refactoring?▼

The best way to apply SOLID principles and design patterns during refactoring is selecting GoF patterns with concrete transformation guidance and trade-off analysis to ensure extensibility across object-oriented modules.

Does this refactoring approach provide concrete steps for fixing code quality issues?▼

Yes, this refactoring approach outputs concrete steps, pattern selections, and rationale for fixing code quality issues, emphasizing safety checks and measurable improvements across modules.

Can I use these refactoring techniques on object-oriented codebases similar to Java?▼

Yes, you can use these refactoring techniques on Java or similar object-oriented codebases to evaluate maintainability, extensibility, and SOLID adherence across modules.

When should I not use automated design pattern recommendations for code refactoring?▼

You should avoid automated design pattern recommendations when safety checks cannot be validated or when the object-oriented codebase lacks measurable improvement metrics to justify the refactoring steps.