refactor

Guide users through interviews to create refactoring plans and GitHub issues.

Updated May 5, 2026

Search Tags:#code quality #development workflow #refactoring #github #technical debt #software architecture

Ready to run

npx skills add https://github.com/wachawo/claude-skills --skill refactor-wachawo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: refactor
Source: https://github.com/wachawo/claude-skills/tree/main/skills/refactor
Command: npx skills add https://github.com/wachawo/claude-skills --skill refactor-wachawo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity and risk associated with large-scale code refactoring by providing a structured, interview-based approach to planning and execution.

Core Features & Use Cases

Structured Planning: Guides the user through an interview process to define scope, alternatives, and implementation details.
Incremental Execution: Breaks down complex changes into tiny, safe, and verifiable commits following industry best practices.
Documentation: Automatically generates a comprehensive GitHub issue template including decision logs, testing strategies, and out-of-scope items.

Quick Start

Ask the refactor skill to help you plan a safe refactoring strategy for the current module.

Frequently Asked Questions about refactor

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

FAQPage Schema

How do I plan a safe code refactoring strategy for a large module?▼

Safe code refactoring requires a structured planning approach to mitigate risks. This Skill uses an interview-based process to define scope, assess test coverage, and break complex architectural changes into tiny, verifiable commits.

What is the best way to break down technical debt into incremental changes?▼

Breaking down technical debt into incremental changes involves defining implementation details and out-of-scope items. A guided planning process ensures complex modifications are executed safely with clear architectural documentation.

How do I document software architecture changes for a GitHub issue?▼

Documenting software architecture changes for a GitHub issue requires a comprehensive template. This includes decision logs, testing strategies, and clear communication of technical implementation steps to track refactoring progress.

Can I use this refactoring approach for any software engineering task?▼

This refactoring approach applies to software engineering tasks requiring safe, incremental code changes. It is best suited for projects needing risk mitigation, test coverage assessment, and architectural documentation.

What should be included in a refactoring plan to ensure safe code changes?▼

A refactoring plan for safe code changes should include scope, alternatives, and testing strategies. It must also document decision logs and out-of-scope items to ensure clear communication of technical implementation steps.