codehub-refactoring

Refactoring support with OpenCodeHub

OpenCodeHub's MCP surface is read-only with respect to your source — no tool edits the working tree. This skill uses the graph to plan a refactor (map the blast radius and every reference before you touch anything) and to verify it afterward (confirm the diff matches the plan and nothing unexpected moved). The actual edits are made by you or your editor; OpenCodeHub tells you exactly what to change and then checks your work.

When to Use

• "What will break if I rename validateUser?"
• "Map every caller before I extract this into a module."
• "Where are all the references to this symbol — including dynamic ones?"
• "I just refactored — did the change touch only what I expected?"
• Any rename, extract, split, or move where you need the dependency picture before editing and a verification pass after.

Workflow

PLAN
1. mcp__codehub__impact({ name: target, direction: "upstream" })   → All dependents (the edit list)
2. mcp__codehub__context({ name: target })                         → Incoming / outgoing refs + processes
3. mcp__codehub__shape_check (if the symbol is a route/payload)    → Producer/consumer drift to watch
4. Build the edit plan from impact's d=1 set + context's refs

APPLY (you / your editor — OpenCodeHub does not do this)
5. Make the edits in your editor or with the language server's rename

VERIFY
6. mcp__codehub__detect_changes({ scope: "unstaged" })             → What the diff actually touched
7. Cross-check changed_symbols against the plan — any surprise is a miss
8. Run tests for the affected processes

If the context envelope warns the index is stale, run codehub analyze first — a stale graph produces an incomplete plan and a misleading verification.

Checklists

Plan and verify a symbol rename

PLAN
- [ ] mcp__codehub__impact({ name, direction: "upstream" }) — enumerate every dependent; this is your edit list
- [ ] mcp__codehub__context({ name }) — see inbound + outbound refs, including ACCESSES edges
      (pass `file_path` and/or `kind` to disambiguate when the name is ambiguous)
- [ ] Note the confidenceBreakdown: `unknown > 0` means a heuristic edge the SCIP
      oracle contradicted — inspect those by reading source before trusting them
- [ ] Watch for dynamic references the graph cannot see (string-keyed dispatch,
      reflection, config JSON, doc comments) — list them as manual-check items

APPLY (your editor / LSP rename — not an OpenCodeHub tool)
- [ ] Apply the rename across the files impact + context named

VERIFY
- [ ] mcp__codehub__detect_changes({ scope: "unstaged" }) — confirm the diff scope
- [ ] Cross-check detect_changes against impact's d=1 count — a gap means a missed reference
- [ ] Run tests for every affected process