ide-deps

## 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 (call hierarchy, references, document symbols) 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) Alternative: `/ide-diagnostics-board` works without the bridge for diagnostics." - **Available**: call it. If `extensionConnected` is `false`: show the same message. If `true`: proceed. Generate an interactive dependency graph for the given file or symbol and open it in the browser. ## Arguments `$ARGUMENTS` may be: - A file path: `src/bridge.ts` - A file + symbol: `src/bridge.ts:handleConnection` If no arguments provided, call `getOpenEditors` and use the first active editor's file path. ## Steps ### Phase 1 — Identify target 1. Parse `$ARGUMENTS` to extract the file path and optional symbol name. 2. Call `openFile` on the resolved path to ensure it is loaded. 3. Call `getDocumentSymbols` on the file to list all exported functions and classes. 4. If a symbol name was specified, filter to that symbol only. Otherwise use all exported symbols (cap at 20 symbols to keep the graph readable). ### Phase 2 — Buil...