Coordinates safe refactoring of duplicated Java/C++ code in TDD cycles.
npx skills add https://github.com/craigtkhill/atui-tools --skill refactor-craigtkhill
Please help me install this Agent Skill. Skill: refactor Source: https://github.com/craigtkhill/atui-tools/tree/main/skills/refactor Command: npx skills add https://github.com/craigtkhill/atui-tools --skill refactor-craigtkhill
This Skill guides developers through the REFACTOR phase of the RED-GREEN-REFACTOR cycle in Test-Driven Development. It emphasizes a search-first mindset to identify duplication, improve patterns, and apply safe refactoring strategies.
Refactor the codebase with duplicated logic by following this workflow: identify duplicates, plan a single abstraction, implement changes incrementally, and verify all tests pass after each step.
High-intent search queries and answers about installing and using this skill.
Eliminate duplication by following the refactor phase of Test-Driven Development: search for existing patterns first, analyze whether duplication should be unified, choose a refactoring strategy (extract function, parameterize, extract interface, or introduce abstraction), then implement incrementally with all tests passing after each change.
Use a search-first approach to identify duplications, plan a single abstraction, implement changes in small incremental steps, and run all tests after each change. Keep all tests green before refactoring, revert if needed, and keep refactoring separate from feature work.
Ask critical questions during duplication analysis: can the duplication be safely unified into a single abstraction, or would combining it create unwanted coupling? Refactor only when unification improves patterns without changing behavior, and always verify tests pass before and after changes.
Refactoring strategies depend on duplication scope and coupling risk. Extract function for isolated duplicated logic, parameterize for similar functions with varying inputs, extract interface for shared behavior across types, and introduce abstraction for complex pattern drift.
No. Keep refactoring separate from feature work to maintain a safe, predictable workflow. Complete feature cycles in the red-green-refactor pattern, then perform refactoring in dedicated phases with all tests green, ensuring changes don't alter behavior.
Searching for existing patterns and duplications first prevents unnecessary changes and redundant abstractions. This approach identifies what already exists in the codebase, reduces over-engineering, and ensures refactoring decisions are informed by the actual code structure.
yonRestructure existing code without changing external behavior, verified by a test suite.
Atrium-HermesGenerate four skill variations, score them against a rubric, and commit the winner as a PR.
HankLiu447Guide red-green-refactor cycles by writing failing tests before code.
CloakingGhostAutomate code review, error fixing, and structural improvements via static analysis.
