lsp-validation

Validate code diagnostics, navigation, and safe renaming via LSP tooling.

17|1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/jakezp/everything-opencode --skill lsp-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lsp-validation
Source: https://github.com/jakezp/everything-opencode/tree/main/skills/lsp-validation
Command: npx skills add https://github.com/jakezp/everything-opencode --skill lsp-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure code correctness and maintainability by leveraging Language Server Protocol tooling for diagnostics, navigation, and safe refactoring.

Core Features & Use Cases

  • Diagnostics: fetch and interpret lsp_diagnostics across files to surface errors and warnings.
  • Navigation: jump to definitions and easily locate symbol usages with lsp_goto_definition and lsp_find_references.
  • Refactoring: perform safe symbol renames using lsp_rename and verify impact with references.
  • Use Case: Before releasing a feature, run diagnostics to catch type errors, verify symbol definitions, and safely rename identifiers if needed.

Quick Start

Run lsp_diagnostics on a TypeScript file to locate errors, then jump to the error's definition with lsp_goto_definition.

Frequently Asked Questions about lsp-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run LSP diagnostics to check code health before a release?

You can validate code health by running LSP diagnostics across files to fetch and interpret errors and warnings. This surfaces type issues and navigates to their definitions before releasing a feature.

What is the safest way to rename symbols and verify their references?

The safest way to rename symbols is using LSP refactoring workflows that perform safe renames and verify impact with references. This ensures all symbol usages are updated correctly across the codebase.

Can I use go-to-definition and find references for any language supported by an LSP server?

Yes, go-to-definition and find references work across any language supported by LSP servers. This navigation tooling allows you to jump to symbol definitions and easily locate all symbol usages within your software projects.

How do I locate the definition of an error found during code diagnostics?

To locate the definition of an error found during code diagnostics, use the go-to-definition functionality. This jumps directly to the symbol definition causing the diagnostic warning or error in your file.

Do I need specific dependencies installed to use LSP tooling for refactoring?

No specific dependencies are required to use this LSP tooling for refactoring. It orchestrates diagnostics, symbol navigation, and safe renaming workflows natively across languages supported by your existing LSP servers.