ide-refactor

# IDE Safe Refactor Workflow ## Prerequisites 1. Check if the `getToolCapabilities` MCP tool is available to you. - **Not available** (no MCP tool by that name): stop and tell the user: "This skill requires the Claude IDE Bridge with a connected VS Code extension. It uses LSP tools (rename symbol, code actions, references, snapshots) that have no CLI equivalent. To use this skill: 1. Start the bridge: `npm run start-all` (in claude-ide-bridge/) 2. Ensure the Claude IDE Bridge extension is installed in your IDE 3. Use the `claude --ide` session (not remote-control)" - **Available**: call it. If `extensionConnected` is `false`: show the same message. If `true`: proceed. Perform refactoring with a safety net. Uses snapshots for instant rollback if tests fail after the change. ## Workflow ### Phase 1: Checkpoint 1. Use `createSnapshot` with name "pre-refactor" to capture current workspace state 2. Confirm: "Snapshot created. Starting refactoring: $ARGUMENTS" ### Phase 2: Plan the refactoring 3. Analyze what needs to change based on the description: `$ARGUMENTS` 4. Use `searchWorkspace` and `getDocumentSymbols` to identify all affected symbols 5. Use `findReferences` to map the impact across the codebase 6. Use `getCallHierarchy` to understand dependency chains 7. List all files that will be affected and confirm the plan ### Phase 3: Execute the refactoring For symbol renames: 8. Use `refactorAnalyze` on the target symbol first: - Retur...