Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fradser/request-refactor-plan
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue.
Passed 8 of 20 test cases with the skill, and 11 of 20 without it.
and 1 more in the full report
4 fixed5 passed either way6 still failing7 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to clean up the monolithic payment processing service in our application. Please lead me through a complete refactoring planning session—investigating the repo, discussing architectural alternatives, interviewing me on exact scope and testing, and finally filing a GitHub issue that lays out the change plan in tiny, working steps.
| Checked | Without skill | With skill |
|---|---|---|
| Asks the user to provide their own ideas for potential solutions. | Missed | Passed |
The instructions your model reads when the skill loads.
Go through the steps below. Skip steps not considered 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:
test cases passed, vs 11 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.