Refactoring Patterns

What it does

This skill helps AI agents guide code review and refactoring efforts by applying established refactoring patterns. It provides a disciplined approach to improving existing code's internal structure without altering its observable behavior, focusing on small, test-backed transformations. The goal is to reduce technical debt and prepare code for new features using named refactorings that address specific "code smells."

When to use it

• During code reviews to identify areas needing improvement.
• When preparing existing codebases for the addition of new features.
• To systematically reduce technical debt within a project.
• When encountering common code smells like Long Method or Duplicate Code.
• To assess and improve the structural quality of code, aiming for a score of 10/10 based on defined principles.

Key capabilities

• Code Smell Identification: Recognizes and names various code smells (e.g., Feature Envy, Long Method, Duplicate Code).
• Refactoring Pattern Application: Suggests specific refactorings to address identified code smells.
• Structural Quality Scoring: Evaluates code structure on a scale of 0-10 based on defined principles.
• Provides Remediation Steps: Offers guidance on the steps needed to reach a structural quality score of 10/10.
• Categorizes Smells: Groups smells into five families: Bloaters, Object-Orientation Abusers, Change Preventers, Dispensables, and Couplers.

Example prompts

• "Review this code snippet for any code smells and suggest refactorings."
• "Assess the structural quality of this function (provide code) and tell me how to improve it."
• “What refactoring should I apply to address a ‘Long Method’?”

Tips & gotchas

• The skill focuses on refactoring, not rewriting. It's about improving structure, not changing functionality.
• Always ensure tests pass after applying any suggested refactorings.
• This skill is designed for backend services and APIs workflows.