Before changing many files at once, you need a clear plan. This skill helps you create that plan step by step. It looks at your code first to understand what needs to change.
The plan lists every file that will be affected. It shows the order to make changes safely. You start with types, then code, then tests, then cleanup. Each phase has a way to check it worked.
The skill stops after making the plan and asks for your confirmation before any edits. This avoids mistakes and keeps your project stable. It also includes a rollback plan in case something goes wrong.
Global
mkdir -p ~/.claude/skills/refactor-planProject
mkdir -p .claude/skills/refactor-planSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective