claude-ide-bridge: Skill for Claude Code

Generate a visual diagnostics dashboard for the workspace and open it in the browser.

Prerequisites

1. Check if the getToolCapabilities MCP tool is available to you.
   • Available: call it, check extensionConnected → use IDE Path below.
   • Not available (no MCP tool by that name): use CLI Path below.

Arguments

$ARGUMENTS sets the severity filter:

• error — errors only
• warning — warnings and errors
• all (default) — all severities

---

IDE Path

Use this path when bridge MCP tools are available.

Phase 1 — Collect diagnostics

1. Determine the severity filter from $ARGUMENTS (default: all).
2. Call getDiagnostics with no URI filter (full workspace scan). Pass the severity param if supported.
3. If no diagnostics found, report "No diagnostics found — workspace is clean." and stop.

Phase 2 — Summarize

1. Group diagnostics by severity: errors / warnings / info / hints.
2. Group by file: sort files by error count descending.
3. Compute totals: total diagnostic count, count per severity, number of files affected.

Phase 3 — Generate and open HTML

1. Construct the HTML document (see HTML Template section below).
2. Call openInBrowser with the HTML string and filename diagnostics-<timestamp>.html.
3. Report: "Opened diagnostics board — N errors, M warnings across K files. Saved to: "

---

CLI Path

Use this path when bridge MCP tools are NOT available (e.g., remote-control sessions).

Phase 1 — Detect and run linters

1. Determine the severity filter from $ARGUMENTS (default: all).
2. Detect which linters are available by checking for config files using Glob:
   • **/tsconfig.json (not in node_modules) → run via Bash: npx tsc --noEmit 2>&1
   • **/biome.json or **/biome.jsonc → run via Bash: npx biome check . --reporter=json 2>&1
   • **/.eslintrc* or **/eslint.config.* → run via Bash: npx eslint . --format json 2>&1
   • **/pyrightconfig.json or **/*.py → run via Bash: npx pyright --outputjson 2>&1
   • **/ruff.toml or **/pyproject.toml → run via Bash: ruff check . --output-format json 2>&1
   • **/Cargo.toml → run via Bash: cargo check --message-format json 2>&1
3. If no linters detected, report "No linter configuration found in workspace." and stop.