lsproxy-cli

Drive the lspeasy CLI programmatically for scripted refactor workflows.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/pradeepmouli/lspeasy --skill lsproxy-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lsproxy-cli
Source: https://github.com/pradeepmouli/lspeasy/tree/main/apps/cli/skills/lsproxy-cli
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill lsproxy-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Programmatic control over the lspeasy CLI to embed LSP tooling into automated workflows, enabling scripted refactors and workspace edits without manual CLI interaction.

Core Features & Use Cases

  • Exposes a programmatic entry point for the lspeasy CLI to run namespace commands, workspace edits, and session management from scripts.
  • Supports integration in CI/CD pipelines, tooling orchestrations, and editor/tooling integrations that require automated LSP tooling via a typed, JS/TS API.
  • Use Case: integrate lsproxy-cli into a build pipeline to apply a WorkspaceEdit to a project and report the applied changes.

Quick Start

Run lsproxy-cli from your script to trigger a WorkspaceEdit or RefactorSession workflow against your project.

Frequently Asked Questions about lsproxy-cli

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

FAQPage Schema
How do I automate LSP refactoring workflows in a CI/CD pipeline?

Automating LSP refactoring workflows in a CI pipeline requires a typed, programmatic entry point to drive the lspeasy CLI. It enables scripts to apply workspace edits and orchestrate refactor sessions without manual interaction.

Can I apply a WorkspaceEdit to a project programmatically using a CLI?

Applying a WorkspaceEdit programmatically is supported by invoking the lspeasy CLI entry point from a script. This allows build pipelines to apply workspace modifications and report the applied changes automatically.

What is a programmatic entry point for scriptable LSP tooling?

A programmatic entry point for LSP tooling exposes a typed API to run namespace commands and manage sessions from scripts. It enables integration into tooling orchestrations requiring predictable automation for refactoring.

Do I need a typed JS/TS API to orchestrate LSP refactor sessions?

Orchestrating LSP refactor sessions benefits from a typed JS/TS API to ensure predictable automation. The CLI integration supports SessionOptions and references-driven design to satisfy typed interfaces for reliable scriptable workflows.

Does lsproxy-cli work with build pipelines for automated namespace commands?

lsproxy-cli works with build pipelines by providing a programmatic interface to run namespace commands and workspace edits. It targets integration into tooling orchestrations requiring automated LSP tooling without manual CLI interaction.