Refactoring
38 portable Agent Skills for disciplined, reviewable AI-assisted work across Codex, Claude Code, GitHub Copilot, and compatible agents.
npx -y skills add nevitonsantana/adaptive-skills --skill refactoringAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Improve structure and clarity incrementally while protecting behavior and rollback options.
SKILL.md
1.8 KB, as published. Nobody here has run it
Overview
Use this skill when the code works but is too costly to reason about or change safely.
When to Use
- structural cleanup
- duplication reduction
- local complexity reduction
When NOT to Use
- urgent bug response without a stable repro
- large rewrites justified only by taste
Core Moves
- Name the reason for refactoring.
- Define the behavior that must remain stable.
- Choose the smallest safe sequence.
- Validate after each meaningful step.
Optional Modules
- Extraction pass — Pull out a smaller unit when a file or function does too much.
- Naming pass — Rename concepts once structure is clearer.
- Rollback plan — Clarify how to stop or revert if the cleanup becomes risky.
Activation Triggers
- Use extraction when responsibilities are mixed.
- Use naming when the main confusion is semantic rather than structural.
- Use rollback planning when the refactor touches core paths.
Expected Output
- clear refactoring objective
- incremental change set
- behavior-preservation evidence
Verification
- The change removed complexity rather than moving it around.
- Behavior was checked after meaningful steps.
- The refactor stayed inside its declared boundary.
Handoff Signals
- The cleanup exposes a larger architectural issue.
- The next safe step belongs to another owner or specialty.
Pairs Well With
code-styletestingarchitecture-review
Anti-patterns
- Calling a rewrite a refactor.
- Mixing cleanup and new behavior without saying so.
- Expanding scope because the codebase “needs it anyway.”