lsp-implement

Identify concrete types implementing a specified interface or abstract type.

102|5|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lsp-implement
Source: https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-implement
Command: npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify every concrete type that satisfies the specified interface or abstract type, enabling safe refactors and accurate polymorphic understanding.

Core Features & Use Cases

  • Locate the interface or abstract type definition.
  • List every concrete type that implements or extends it, across the workspace.
  • Cross-reference with type hierarchy when available to reveal subtypes and supertypes, and generate a structured implementation report.
  • Use before changing a public API to ensure all affected implementations are updated.

Quick Start

Provide the interface or abstract type name to identify all concrete implementations.

Frequently Asked Questions about lsp-implement

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

FAQPage Schema
How do I find all concrete implementations of an interface before refactoring?

To find concrete implementations of an interface for safe refactoring, this Skill cross-references the agent-lsp server's go_to_implementation and type_hierarchy features to list every impacted type across a workspace.

What is the best way to enumerate subtypes and supertypes for polymorphism analysis?

For polymorphism analysis, type hierarchy cross-referencing reveals subtypes and supertypes by locating the abstract type definition and verifying server capabilities to produce a complete structured implementation report.

Does the lsp-implement Skill work without an active language server?

No, this Skill requires an active agent-lsp server connection because it explicitly verifies server capabilities and relies on go_to_implementation support to enumerate concrete types.

How do I locate every concrete type that satisfies a specified abstract type?

You locate every concrete type satisfying an abstract type by providing the interface name, which triggers a workspace-wide search using go_to_implementation features to identify all extending implementations.

Why does changing a public API signature require checking type implementations?

Changing a public API signature requires checking type implementations because failing to enumerate impacted implementations risks breaking concrete types that satisfy the interface across the workspace.