ide-review

# IDE PR Review 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 (hover, references, call hierarchy, diagnostics) and GitHub tools for deep PR analysis. 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: use `gh pr diff <number>` for a basic diff review." - **Available**: call it. If `extensionConnected` is `false`: show the same message. If `true`: proceed. Review a pull request using the IDE bridge's full code intelligence stack. Goes beyond diff reading by using LSP to understand the impact of changes. ## Workflow ### Phase 1: Gather PR context 1. Use `githubViewPR` to get PR details (title, description, author, base branch): `$ARGUMENTS` 2. Use `githubGetPRDiff` to get the full diff 3. Use `githubListRuns` to check CI status on the PR branch ### Phase 2: Deep code analysis For each changed file in the diff: 4. Use `openFile` to open the file at the first changed line 5. Use `getDiagnostics` to check for any errors or warnings in modified files 6. For each modified function or class: - Use `getHover` to verify type signatures are correct - Use `f...