Refactor and Clean Code for Maintainability
Refactors tangled code into clean, maintainable code using SOLID design patterns and an incremental, behavior-stable refactor plan.
Why it matters
Improve code quality by refactoring tangled or hard-to-maintain code, reducing duplication and complexity while enhancing testability and design consistency.
Outcomes
What it gets done
Analyze code for smells, dependencies, and risky hotspots.
Develop a refactor plan with incremental steps.
Apply changes incrementally, ensuring behavior stability and passing tests.
Update tests to verify regressions and maintain code integrity.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-code-refactoring-refactor-clean | bash Overview
Refactor and Clean Code
A refactoring skill improving code quality and maintainability using SOLID design patterns and an incremental, behavior-stable plan. Use for refactoring tangled code or preparing modules for new features; not for one-line fixes, change-freeze periods, or documentation-only requests.
What it does
This skill acts as a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices, analyzing and refactoring provided code to improve its quality, maintainability, and performance while avoiding over-engineering.
Its approach: assess code smells, dependencies, and risky hotspots; propose a refactor plan with incremental steps; apply changes in small slices while keeping behavior stable; update tests and verify regressions. Its safety constraints: avoid changing external behavior without explicit approval, and keep diffs reviewable while ensuring tests pass. Its output format covers a summary of issues and target areas, a refactor plan with ordered steps, proposed changes and expected impact, and test/verification notes. It references a bundled resources/implementation-playbook.md for detailed patterns and examples when needed.
When to use - and when NOT to
Use this skill when refactoring tangled or hard-to-maintain code, reducing duplication/complexity/code smells, improving testability and design consistency, or preparing modules for new features safely.
Not for a small one-line fix, when refactoring is prohibited due to a change freeze, or for documentation-only requests.
Inputs and outputs
Inputs: code to refactor, plus any specific requirements or constraints for the refactor.
Outputs: a summary of code smells and target areas, an ordered incremental refactor plan, the proposed changes with expected impact, and test/verification notes confirming behavior stability.
Integrations
A bundled resources/implementation-playbook.md for detailed patterns and examples.
Who it's for
Developers refactoring tangled or hard-to-maintain code who need an incremental, behavior-preserving plan grounded in SOLID and clean code principles.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.