refactor
Skill88 starsChanged 8 months agoMITView on GitHub
Systematic code refactoring - analysis, pattern detection, incremental changes with verification. Use for code improvement and tech debt reduction.
195 other projects use a version of this.
Adopted by
Most recently taken up by
- Archont561/skillstheir own version, first seen Nov 15, 2026
- nazmirket/skillstheir own version, first seen Nov 15, 2026
- qivora-labs/agentinittheir own version, first seen Nov 15, 2026
- NomadicDaddy/aiddtheir own version, first seen Nov 15, 2026
- zircote-plugins/refactortheir own version, first seen Nov 15, 2026
- vlad-ryzhkov/ai-context-engineering-for-frontendtheir own version, first seen Nov 15, 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
parcadeiSkillagentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +8 more from parcadei
Other versions195 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 195
- 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★ 715same name
- membrane/api-gateway★ 658same name
185 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 repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bug-fixSkill
- deploy-checkSkill
- dev-setupSkill
- orchestratorSkill
- pre-release-checkSkill
- qa-pipelineSkill
- refactor-analysisSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 168 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
Create a focused commit
- Very specific: line 41
Run tests after each change: cargo test
- Distinctive: line 42
Verify no behavior changes
- Distinctive: line 43
Update documentation if needed
- Distinctive: line 55
Never change behavior and refactor in the same commit
- Distinctive: line 56
Run tests after every change
- Distinctive: line 57
Keep commits small and focused
- Distinctive: line 58
If unsure about a refactoring, ask before proceeding
“Common” is measured: kept by at least 6 in 10 of the 168 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
Code Refactoring Workflow
Refactor target: $ARGUMENTS
Step 1: Code Analysis (parallel)
cargo clippy -- -W clippy::all -W clippy::pedantic
tokei src/
rg "TODO|FIXME|HACK" src/Step 2: Pattern Detection
Identify these code smells:
- Duplicate code: Similar logic in multiple places
- Long functions: Functions > 50 lines
- Complex types: Structs with > 10 fields
- Deep nesting: > 3 levels of indentation
- Magic numbers: Hardcoded values without constants
- Inconsistent error handling: Mixed error patterns
Step 3: Refactoring Plan
Prioritize targets and plan changes:
- Module organization (split large files)
- Function decomposition (single responsibility)
- Type safety improvements (enums over strings, newtypes)
- Performance optimizations (iterators, reduce allocations)
Step 4: Incremental Refactoring
For each change:
- Create a focused commit
- Run tests after each change:
cargo test - Verify no behavior changes
- Update documentation if needed
Step 5: Verification
cargo test
cargo clippy -- -D warnings
git diff --statGuidelines
- Never change behavior and refactor in the same commit
- Run tests after every change
- Keep commits small and focused
- If unsure about a refactoring, ask before proceeding
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.

