ide-diagnostics

liby's avatarfrom liby

Expert knowledge of IDE/LSP tools for code navigation, diagnostics, and refactoring. Use when working with TypeScript errors, linting issues, code navigation, or IDE operations.

⭐23stars🔀2forks📁View on GitHub🕐Updated Jan 1, 2026
[Developer Tools]

When & Why to Use This Skill

This Claude skill provides expert-level integration with IDE and LSP (Language Server Protocol) tools to streamline code navigation, diagnostics, and refactoring. It empowers developers to identify TypeScript errors, perform safe symbol renaming, and execute automated code improvements directly within their development environment, significantly enhancing coding productivity and accuracy.

Use Cases

  • Identifying and fixing TypeScript errors and linting issues by retrieving real-time diagnostics from the language server.
  • Performing safe, scope-aware symbol renaming across the entire codebase to maintain structural integrity without manual find-and-replace errors.
  • Conducting impact analysis by finding all references and callers of a specific function or class before refactoring.
  • Automating routine code maintenance tasks such as organizing imports, formatting documents, and applying bulk 'fix-all' commands.
  • Validating code changes by checking diagnostic messages before committing to ensure no new warnings or errors were introduced.
nameide-diagnostics
descriptionFix TypeScript errors, get diagnostics, rename symbols, find references, organize imports. Use when user needs IDE/LSP tools for code navigation, diagnostics, and refactoring.
version0.1.0
user-invocablefalse

IDE Diagnostics and Navigation Expert

Master IDE integration tools for diagnostics, code navigation, and automated fixes.

Available IDE Tools

Get Diagnostics (mcp__ide__getDiagnostics)

Retrieve errors, warnings, and info messages from the IDE's language server.

When to use: Before fixing errors, checking linting, validating changes

Find References (mcp__ide__get_references)

Find all usages of a symbol (variable, function, class, etc.)

When to use: Before renaming, understanding impact, finding callers

Rename Symbol (mcp__ide__rename_symbol)

Safely rename across the entire codebase.

ALWAYS use this instead of manual find-replace - handles scope correctly.

Execute IDE Command (mcp__ide__execute_command)

Execute IDE commands like auto-fix, organize imports, format document.

Common commands:

  • editor.action.fixAll - Auto-fix all issues
  • editor.action.organizeImports - Remove/sort imports
  • editor.action.formatDocument - Format document

Best Practices

DO:

  • Use mcp__ide__getDiagnostics instead of tsc --noEmit
  • Use mcp__ide__rename_symbol instead of manual find-replace
  • Use editor.action.fixAll instead of eslint --fix or biome check --fix
  • Check diagnostics before committing changes
  • Fix errors before warnings
  • Read file context before fixing (use Read tool)

DON'T:

  • Run tsc --noEmit via Bash when you have getDiagnostics
  • Use Edit tool for renaming (use rename_symbol)
  • Ignore warnings - they often indicate real issues
  • Fix diagnostics without understanding the context

Additional Resources

Troubleshooting

No Diagnostics Returned

Possible causes:

  • IDE not running or not connected
  • File not opened in IDE
  • Language server not initialized

Diagnostics Not Updating

After fixes, diagnostics may take a moment to refresh. If needed:

  • Use editor.action.fixAll
  • Save the file
  • Re-run getDiagnostics

References