lsp-implement

Solid

Find all concrete implementations of an interface or abstract type. Use when you need to know what types satisfy an interface, or what subtypes exist before changing a base type.

AI & Automation 56 stars 2 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
58
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

> Requires the agent-lsp MCP server. # lsp-implement Find every concrete type that implements an interface, or every subtype of an abstract type. Read-only — does not modify any files. Use this skill **before** changing an interface signature, adding a method to an interface, or removing a base-type method. It tells you every type that must be updated. **Invocation:** User provides `type_name` (e.g. `"Handler"`, `"io.Reader"`). Optionally provide `workspace_root`. --- ## Prerequisites Check server capabilities — `go_to_implementation` and `type_hierarchy` are optional features not implemented by all language servers: ``` mcp__lsp__get_server_capabilities() ``` Note which of `go_to_implementation` and `type_hierarchy` appear in `supported_tools`. The steps below depend on this result. If neither is supported, report `"Server does not support implementation lookup"` and stop. --- ## Step 1 — Locate the interface or type ``` mcp__lsp__go_to_symbol({ "symbol_path": "<TypeName>", "workspace_root": "/abs/path" // optional }) → returns: file, line, column (1-indexed) ``` Open the file so the language server tracks it: ``` mcp__lsp__open_document({ "file_path": "<file from go_to_symbol>" }) ``` Record `file`, `line`, `column` for subsequent steps. --- ## Step 2 — Find all implementations Only if `go_to_implementation` appears in `supported_tools`. ``` mcp__lsp__go_to_implementation({ "file_path": "<file>", "line": <line>, "column": <column> }) ``` R...

Details

Author
blackwell-systems
Repository
blackwell-systems/agent-lsp
Created
2 months ago
Last Updated
today
Language
Go
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

lsp-setup

Configure a Language Server (LSP) for a specific language so editor/agent tooling — diagnostics, go-to-definition, find-references, rename — works. Use when you need to: configure LSP, lsp setup, set up or install a language server, fix 'no LSP server configured' / 'server not installed', choose between servers (basedpyright vs pyright vs ty vs ruff), or wire .codex/lsp-client.json / .opencode/lsp.json. 언어서버 설정. Routes by file extension to references/<language>/README.md for the exact builtin server, per-OS install commands (macOS/Linux/Windows), config snippets for both config files, initialization options, alternatives, and troubleshooting. Ships scripts: detect-lsp.ts (scan a project for languages + each server's install/config status) and verify-lsp.ts (run a real diagnostics roundtrip). Covers typescript, python, go, rust, c/c++, java, kotlin, c#/razor, swift, ruby, php, dart, elixir, zig, lua, bash, yaml, terraform, haskell, julia.

61,980 Updated today
code-yeongyu
AI & Automation Solid

lsp-local-symbols

Fast file-scoped symbol analysis — find all usages of a symbol within the current file, list all symbols defined in the file, and get type info at a position. Use when you need local-scope analysis without a workspace-wide search.

56 Updated today
blackwell-systems
AI & Automation Listed

lsp

Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.

60,341 Updated 1 weeks ago
code-yeongyu