refactor
/refactor
Safe refactoring with dependency awareness. Use when restructuring, renaming, moving, extracting, or consolidating code.
- Author
- jordancoin ↗
- Repository
- codemap ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Safe refactoring with dependency awareness. Use when restructuring, renaming, moving, extracting, or consolidating code.
Original author description
Safe refactoring with dependency awareness. Use when restructuring, renaming, moving, extracting, or consolidating code.
How it works
- Before refactoring
- Refactoring checklist
- Safe rename pattern
- Safe move pattern
- After refactoring
SKILL.md preview
--- name: refactor description: Safe refactoring with dependency awareness. Use when restructuring, renaming, moving, extracting, or consolidating code. --- # Safe Refactoring with Code Intelligence ## Before refactoring 1. Run `codemap --deps .` to understand the dependency graph 2. Identify hub files in the refactoring scope: they need extra care 3. Run `codemap --diff` to see what's already changed on this branch ## Refactoring checklist - [ ] All tests pass before starting - [ ] Hub files identified and dependents listed - [ ] Public API changes planned (additive preferred) - [ ] Import paths updated if moving files - [ ] No circular dependencies introduced ## Safe rename pattern 1. Add the new name alongside the old (alias/wrapper) 2. Update all callers to use the new name 3. Remove the old name 4. Run full test suite ## Safe move pattern 1. Create the new file with the same API 2. Re-export from the old location (temporary) 3. Update all importers to use the new path 4. Remove the old file and re-export ## After refactoring - Run `codemap --deps .` again to verify the graph is clean - Run `codemap --importers <moved-file>` to check nothing is broken - Full test suite must pass
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jordancoin/codemap | 90 | MIT |
| froglet-studio/cosmic-shore | 100 | MIT |
| mgiovani/cc-arsenal | 100 | MIT |
| jongio/skills | 100 | MIT |
| boshu2/agentops | 100 | Apache-2.0 |
| y-miyazaki/terraform-aws-base | 100 | Apache-2.0 |
| mickeyyaya/evolve-loop | 100 | Apache-2.0 |
| j0hanz/j0hanz-marketplace | 100 | MIT |
| kriscard/kriscard-claude-plugins | 100 | MIT |
Database snapshot: 13.11.2026 · package version de283ba64a0d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 85Refactoring
This skill should be used when the user asks to "refactor code", "rename function", "extract method", "reduce complexity", "migrate code", "code migration", "modernize code", "split class", "move code", or mentions code restructuring and refactoring operations. - 100refactoring
Changes code structure without changing behaviour. Use when the user asks to refactor, clean up, restructure, extract, rename across files, reduce duplication, or improve the architecture. Not for features, bug fixes or reviews. - 100refactor-safely
Restructure, rename, split or move code without changing behaviour, and prove that nothing changed. Use this for any refactor, cleanup, file move, module split or dead code removal, including when it is only one step inside a larger task. - 100dev-refactor
Use when changing structure without changing behavior: restructure, extract, rename, dedupe or split code. - 100safe-refactor
Restructure code without changing behaviour - extract, move, consolidate duplicates or remove dead code - with verification before and after every step. Use when a task asks for cleanup or restructuring. Not during active feature work in the same area, right before a release, or… - 95refactoring
Reshape code while preserving behavior, using a passing behavior pin before and after each structural step. Use for renaming, extracting, inlining, moving, deduplicating, architecture improvement reports, module deepening, internal caller migration and deletion, external…