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. The safety net is **git**: the working tree is verified clean before anything is touched, so `git checkout` reverts the whole change if tests fail afterwards. ## Workflow ### Phase 1: Checkpoint There is no snapshot tool. Git is the rollback mechanism, and it only works if the tree is clean first — otherwise a revert would discard the user's unrelated work along with the refactoring. 1. Call `getGitStatus`. - **Clean tree**: proceed. `git checkout -- .` will revert everything this skill does. - **Uncommitted changes present**: stop and offer the choice — "You have uncommitted changes. I can't offer a clean rollback until they're saved. Commit them, or shall I `gitStash` them first and restore them after?" Neve...