braydio/CUSTODIAN / .claude/skills/refactor-safely
refactor-safely
VerifiedPlan and execute safe refactoring using dependency analysis
Refactor Safely
Use the knowledge graph to plan and execute refactoring with confidence.
Steps
- Use
refactor_toolwith mode="suggest" for community-driven refactoring suggestions. - Use
refactor_toolwith mode="dead_code" to find unreferenced code. - For renames, use
refactor_toolwith mode="rename" to preview all affected locations. - Use
apply_refactor_toolwith the refactor_id to apply renames. - After changes, run
detect_changes_toolto verify the refactoring impact.
Safety Checks
- Always preview before applying (rename mode gives you an edit list).
- Check
get_impact_radius_toolbefore major refactors. - Use
get_affected_flows_toolto ensure no critical paths are broken. - Run
find_large_functionsto identify decomposition targets.
Token Efficiency Rules
- In the persistent coordination checkout, start with
get_minimal_context(task="<your task>")when the graph is ready. - In a linked/ephemeral worktree, do not cold-build a graph merely because the first call reports
missing_graph,not_ready, empty/unmapped, or stale coverage. If baseline structural context is useful, point CRG at the persistent coordination root; then verify every implementation/review fact against the current worktree. - If the graph is unusable after one cheap attempt, immediately use targeted symbol/path reads. Current worktree files and
git diffare authoritative for branch-local changes. - When the task packet provides a bounded
## Context Pack, generate it once from the claimed worktree withscripts/ai/pack-context.sh task ...and use it instead of broad file dumping. - Use
detail_level="minimal"on graph calls. Escalate only when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 graph calls and ≤800 graph-output tokens.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |