From shazam
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
npx claudepluginhub qhuang20/shazam --plugin shazamThis skill uses the workspace's default tool permissions.
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.
Creates detailed refactor plans with tiny commits via user interview, checks test coverage, then files as GitHub issue. Use for refactor planning, RFCs, or incremental steps.
Plans structural refactors (rename, extract, move, split, deduplicate) into tiny, green commits via adversarial interview. Outputs markdown plan to docs/refactor-plans; optionally files GitHub issue. Use for refactor proposals, not new features.
Executes multi-phase refactoring with persistent REFACTOR_PLAN.md checkpoints to survive context limits and resume across sessions. For 10+ files or multi-phase changes.
Share bugs, ideas, or general feedback.
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.
After the refactor plan is filed, suggest: "Refactor plan filed! Start implementing, or /grill-me to stress-test the approach."