LSP/Index Engineer

Orchestrate multiple LSP clients to build a unified semantic graph.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/jc180105/.opencode --skill lsp-index-engineer-jc180105
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: LSP/Index Engineer
Source: https://github.com/jc180105/.opencode/tree/main/.opencode/skills/lsp-index-engineer
Command: npx skills add https://github.com/jc180105/.opencode --skill lsp-index-engineer-jc180105

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fragmented language-server ecosystems often yield disjointed code intelligence. LSP/Index Engineer orchestrates multiple LSP clients and builds a unified semantic graph to power accurate navigation, definitions, and references across languages.

Core Features & Use Cases

  • LSP client orchestration across languages (TypeScript, PHP, Go, Rust, Python) to produce a single, cohesive graph.
  • Semantic indexing with nodes for files and symbols and edges for contains, imports, calls, and references; supports real-time incremental updates.
  • LSIF import/export and a SQLite/JSON cache to enable fast startup and offline querying.

Quick Start

Initialize the LSP Index Engineer on a multi-language project and verify that go-to-definition and hover responses remain sub-100ms after changes.

Frequently Asked Questions about LSP/Index Engineer

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

FAQPage Schema
How do I build a unified semantic graph from multiple language servers?

Build a unified semantic graph by orchestrating multiple LSP clients across languages like TypeScript, PHP, Go, Rust, and Python to collect files, extract symbols, and resolve references into a cohesive structure.

How does real-time semantic indexing handle incremental code updates?

Real-time semantic indexing handles incremental code updates by applying caching and scalable graph storage, ensuring go-to-definition and hover responses remain sub-100ms after changes in multi-language codebases.

Can I use LSP orchestration to unify code intelligence across TypeScript and PHP?

Yes, LSP orchestration unifies code intelligence across TypeScript and PHP by collecting files and resolving references from diverse language servers into a single graph for accurate navigation.

What is the best way to import and export LSIF data for offline code querying?

The best way to import and export LSIF data for offline querying is using LSIF import/export capabilities alongside a SQLite/JSON cache, enabling fast startup and offline semantic graph queries.

Does semantic graph construction support cross-language reference resolution?

Semantic graph construction supports cross-language reference resolution by creating nodes for files and symbols with edges for contains, imports, calls, and references, ensuring consistent navigation across diverse language servers.

What are the limitations of building a unified semantic graph with language servers?

Limitations of building a unified semantic graph with language servers include fragmented ecosystems yielding disjointed code intelligence, requiring strict LSP protocol compliance and complex orchestration to maintain consistent cross-language navigation.