refactor
Skill1 starsChanged 5 months agoMITView on GitHub
Refactor code to improve structure, readability, and maintainability without changing behavior. Use when asked to clean up, improve, or restructure code.
196 other projects use a version of this.
Adopted by
Most recently taken up by
- Doist/todoist-aitheir own version, first seen Nov 9, 2026
- Doist/todoist-clitheir own version, first seen Nov 8, 2026
- rvdbreemen/OTGW-firmwaretheir own version, first seen Nov 8, 2026
- paulocsb/worldcup-fifa-pooltheir own version, first seen Nov 8, 2026
- DnsQueen/orcinus-skillstheir own version, first seen Nov 8, 2026
- taixuann/development-spacetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use ascii-diagram, debug-fix and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SethGammonSkillascii-diagram
Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.
Also in 4 projects that use this
zebbernSkilldebug-fix
Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)
Also in 4 projects that use this
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- parcadeiSkill
agentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +8 more from parcadei
Other versions196 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 196
- github/awesome-copilot★ 41ksame name
- unkeyed/unkey★ 5.5ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- adobe/S3Mock★ 1.2ksame name
- SethGammon/Citadel★ 927same name
- poshan0126/dotclaude★ 871same name
- JordanCoin/codemap★ 710same name
- membrane/api-gateway★ 658same name
186 more not listed
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 repository15 other files it gives its agents.
- ci-preflightSkill
- code-reviewSkill
- debugSkill
- docx-processingSkill
- github-publishSkill
- implementSkill
- pdf-processingSkill
- permission-modesSkill
- planSkill
- pptx-processingSkill
- security-testingSkill
- specSkill
- testSkill
- web-developmentSkill
- xlsx-processingSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 169 edited versions we read keep these.
6
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 12
Before touching anything, make sure you know what the code does.
- Distinctive: line 13
Read the module or function in full
- Distinctive: line 40
If there are no tests for the affected code, verify manually
- Distinctive: line 41
If the refactor touches public APIs, update callers
- Distinctive: line 45
Do not add features while refactoring
- Distinctive: line 46
Do not fix bugs while refactoring (unless the bug is in the new code)
“Common” is measured: kept by at least 6 in 10 of the 169 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
Refactoring (Opus 级)
Refactoring changes structure without changing behavior.
Step 1: Understand the current behavior
Before touching anything, make sure you know what the code does.
- Read the module or function in full
- Identify inputs, outputs, and side effects
- Note any existing tests
Step 2: Identify what to improve
Look for:
- Duplicated logic that could be extracted
- Functions that are too long or do too many things
- Poor naming that obscures intent
- Deep nesting that could be flattened
- Mutable state that could be immutable
- Dead code or unused exports
Step 3: Refactor in small, safe steps
Each step should be a single, mechanical transformation:
- Extract function/method
- Rename variable/function
- Move code to more appropriate location
- Simplify conditionals
- Replace loops with functional operations
Step 4: Verify after each step
After each change:
- Run existing tests
- If there are no tests for the affected code, verify manually
- If the refactor touches public APIs, update callers
Step 5: Never mix refactoring with feature work
- Do not add features while refactoring
- Do not fix bugs while refactoring (unless the bug is in the new code)
- Each PR/commit should be either refactoring OR feature work, never both
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.