Analyze refactor requests and produce implementation plans or epics.
npx skills add https://github.com/subroh0508/colormaster --skill refactor-subroh0508
Please help me install this Agent Skill. Skill: refactor Source: https://github.com/subroh0508/colormaster/tree/main/.claude/skills/refactor Command: npx skills add https://github.com/subroh0508/colormaster --skill refactor-subroh0508
This Skill helps teams turn refactor requests into actionable work plans without accidentally changing behavior, by analyzing scope, impact, and the safest execution path.
Ask the refactor skill to analyze your requested change, identify the impacted code and validation points, and draft the appropriate plan or epic.
High-intent search queries and answers about installing and using this skill.
A safe refactor requires touch-file impact analysis and test tracing to generate behavior-preservation verification points. This process identifies affected files and public APIs before you begin codebase cleanup or module reorganization.
The best way to analyze a dependency reduction refactor is by tracing touch-files to map affected modules, tests, and specifications. This impact analysis establishes verification points to confirm inputs, outputs, and UI behavior remain stable.
You route large-scale UI refactors into epics through scale-based routing. This mechanism evaluates the refactor scope to determine if the behavior-preserving changes fit a single implementation plan or require multi-PR epic execution.
Yes, naming standardization is supported by generating implementation plans that trace impacted files and tests. The refactor process applies behavior-preservation checks to ensure public APIs and UI behavior remain stable during standardization.
You should use an epic for a codebase cleanup when the refactor scope demands multi-PR execution. Scale-based routing evaluates the touch-file impact analysis to promote large behavior-preserving changes from a single plan to an epic.
To verify behavior preservation during a client layer rename, the generated plan lists explicit verification points confirming inputs, outputs, and public APIs remain stable. It traces affected tests and specifications to validate the refactor.
Andreicr1Analyzes specifications to map user flows, detect gaps, and output clarifying questions.
pkuppensAlign implementation work with unit tests to validate module behavior.
yalishevantTranslate Java code to Kotlin in Spring applications while preserving behavior and binary compatibility.
subroh0508Draft requirements and design documents from new feature requests.
