Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →syncable-dev/memtrace-refactoring-guide
Build a phased, risk-scored refactoring plan from Memtrace complexity, dead-code, bridge, impact analysis, and Cortex decision-memory constraints.
Passed 12 of 17 test cases with the skill, and 5 of 17 without it.
and 8 more in the full report
10 fixed5 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Candidate handle_checkout was rated High Risk due to wide process involvement. What two specific items must be included in its plan output entry beyond target name and justification?
| Checked | Without skill | With skill |
|---|---|---|
| Includes an incremental migration approach with backward compatibility | Missed | Passed |
| Includes a test plan detailing affected callers or processes | Missed | Passed |
The instructions your model reads when the skill loads.
Guided refactoring workflow — identifies refactoring candidates using structural analysis, scores them by risk and priority, checks Cortex decision memory for rationale/bans/contracts, and produces a phased refactoring plan. Combines complexity metrics, dead code detection, bridge analysis, temporal evolution, and decision memory to prioritize what to refactor first and how to do it safely.
Run these three tools in parallel to build a candidate list:
a) Complexity hotspots:
Call find_most_complex_functions with top_n: 20
b) Dead code:
Call find_dead_code to find unused symbols
c) Architectural bottlenecks:
Call find_bridge_symbols to find chokepoints with too much responsibility
Call get_evolution with from: "90d ago" and mode: "compound".
Review top_touched_symbols and top_changed_files:
Priority matrix:
| Low Complexity | High Complexity | |
|---|---|---|
| Stable (low change freq) | Leave alone | Monitor; refactor if touched |
| Volatile (high change freq) | Normal; leave alone | TOP PRIORITY — refactor first |
For each top-priority candidate, call get_impact with direction: both:
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.