Stats
Actions
Tags
From mattpocock-skills
Interviews the user to create a detailed, incremental refactor plan and files it as a GitHub issue. Useful for scoping safe, step-by-step refactoring work.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mattpocock-skills:request-refactor-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary.
This skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary.
Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
Explore the repo to verify their assertions and understand the current state of the codebase.
Ask whether they have considered other options, and present other options to them.
Interview the user about the implementation. Be extremely detailed and thorough.
Hammer out the exact scope of the implementation. Work out what you plan to change and what you plan not to change.
Look in the codebase to check for test coverage of this area of the codebase. If there is insufficient test coverage, ask the user what their plans for testing are.
Break the implementation into a plan of tiny commits. Remember Martin Fowler's advice to "make each refactoring step as small as possible, so that you can always see the program working."
Create a GitHub issue with the refactor plan. Use the following template for the issue description:
The problem that the developer is facing, from the developer's perspective.
The solution to the problem, from the developer's perspective.
A LONG, detailed implementation plan. Write the plan in plain English, breaking down the implementation into the tiniest commits possible. Each commit should leave the codebase in a working state.
A list of implementation decisions that were made. This can include:
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
A list of testing decisions that were made. Include:
A description of the things that are out of scope for this refactor.
Any further notes about the refactor.
npx claudepluginhub esonhugh/marketplace --plugin mattpocock-skillsInterviews user to plan a refactor, breaks implementation into tiny commits, and files a GitHub issue with a structured plan.
Creates structured, incremental refactoring plans broken into tiny working commits. Use when planning a refactor or breaking down large changes.
DEPRECATED. Guides creation of GitHub issues for refactoring plans with problem/solution, commits, and decisions. Only triggers on explicit `/request-refactor-plan`.