ide-api-deprecation-tracker

# IDE API Deprecation Tracker ## Prerequisites 1. Check if `getToolCapabilities` is available. - **Not available**: tell the user this skill requires the Claude IDE Bridge, then stop. - **Available**: call it. If `extensionConnected` is false: show the same message and stop. If true: proceed. ## Goal Produce a Markdown report of all deprecated APIs ranked by caller count, with migration paths extracted from JSDoc. ## Workflow ### Phase 1: Find deprecated symbols 1. Note the argument: `$ARGUMENTS` - If a scope is given, pass it as the `include` glob to `searchWorkspace` - Otherwise, search workspace-wide 2. Call `searchWorkspace` with pattern `@deprecated` to find all files containing deprecation annotations. This catches: - `/** @deprecated ... */` JSDoc comments - `@deprecated` in TSDoc, Python docstrings, Go comments, etc. 3. For each match, call `getHover` at the annotated symbol's position to extract: - The full deprecation message (migration guidance) - The symbol name and type signature ### Phase 2: Count callers 4. For each deprecated symbol found in Phase 1: - Call `searchWorkspaceSymbols` to locate the symbol's definition precisely - Call `findReferences` on the definition to count all call sites - Record: symbol name, file, line, reference count, deprecation message ### Phase 3: Extract migration paths 5. For symbols with a migration path mentioned in `@deprecated` (e.g., "use `newFunction` instead"): - Extract the re...