refactor-safe
Skill1 starsChanged 41 days agoMITView on GitHub
Refactor code without changing behavior. Use when cleaning structure, renaming, extracting modules, or preparing for a feature.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- Markssuave/Markssuave-Agent-skillstheir own version, first seen Nov 8, 2026
- Vinix24/vnx-orchestrationtheir own version, first seen Nov 1, 2026
- AhmiDarrow/RemedyAItheir own version, first seen Oct 19, 2026
- 0King0P/Claude-Skillstheir own version, first seen Oct 13, 2026
- DailybotHQ/deepworkplan-websitetheir own version, first seen Oct 9, 2026
- AlpayC/claude-skill-settheir own version, first seen Sep 14, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- Vinix24/vnx-orchestration★ 63same name
- DailybotHQ/deepworkplan-website★ 15same name
- AhmiDarrow/RemedyAI★ 5same name
- Markssuave/Markssuave-Agent-skills★ 1same name
- 0King0P/Claude-Skills★ 0same name
- AlpayC/claude-skill-set★ 0same name
- ccpowerpack/claude-code-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository49 other files it gives its agents.
- accessibilitySkill
- address-feedbackSkill
- agent-disciplineSkill
- agent-handoffSkill
- api-designSkill
- architecture-decisionSkill
- brainstormSkill
- browser-verifySkill
- code-reviewSkill
- containerizeSkill
- context-efficientSkill
- create-prSkill
- database-changesSkill
- debug-systematicSkill
- dependency-upgradeSkill
- docs-groundedSkill
- error-handlingSkill
- explore-codebaseSkill
- fix-ciSkill
- frontend-designSkill
- git-commitSkill
- git-worktreeSkill
- incident-triageSkill
- incremental-slicesSkill
- legacy-changeSkill
- migrate-codeSkill
- minimal-diffSkill
- observabilitySkill
- parallel-workSkill
- performance-auditSkill
- plan-before-codeSkill
- python-qualitySkill
- react-componentsSkill
- release-notesSkill
- security-reviewSkill
- setup-ciSkill
- shell-safetySkill
- ship-checklistSkill
- simplify-codeSkill
- skill-authoringSkill
- skill-routerSkill
- spec-drivenSkill
- tddSkill
- threat-modelSkill
- triage-issuesSkill
- typescript-strictSkill
- verify-workSkill
- write-docsSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Keep external APIs stable unless the task requires a break.
- Distinctive: line 12
Prefer automated renames and compiler/type feedback.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Refactor Safe
Rules
- Separate pure refactors from behavior changes; never mix in one commit/PR when avoidable.
- Keep external APIs stable unless the task requires a break.
- Prefer automated renames and compiler/type feedback.
- Preserve existing tests; they are the safety net.
- Take small steps; verify after each step.
Process
- Establish baseline tests/typecheck.
- Make one structural change.
- Re-run baseline.
- Repeat until done.
- Summarize structural changes with no intended behavior delta.
Avoid
- Rewriting working modules “for clarity” beyond the need
- Introducing new patterns not already used in the repo
- Drive-by dependency upgrades during refactors
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.