Eli0shin Cli Lsp Client
eli0shin-cli-lsp-client is a Claude Code plugin for the Build phase that streams LSP, ESLint, and Prettier diagnostics through a background daemon whenever the agent edits JavaScript or TypeScript files.
by eli0shin · github.com/eli0shin/cli-lsp-client
Wire Claude Code edits to a background LSP daemon so TypeScript and JavaScript files get ESLint, Prettier, and language-server diagnostics right after the agent changes code.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install eli0shin-cli-lsp-client@eli0shin/cli-lsp-clientBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:eli0shin/cli-lsp-client") and the paste-ready config with skillselion.get_install_config("plugin:eli0shin/cli-lsp-client").
What it does
eli0shin-cli-lsp-client is a Claude Code plugin family built around a CLI that talks to a long-running LSP client daemon. Solo builders who let Claude rewrite TS/JS constantly lose time when type errors and lint issues only show up at commit time; this setup pushes Language Server Protocol diagnostics, ESLint, and Prettier signals back into the loop as soon as edits land, using hooks so you do not manually re-run checkers. It targets developers shipping web apps or Node tooling with Claude Code as the primary editor, not teams that already rely on a full IDE with built-in LSP. Install the daemon locally, register the plugin bundle, and keep coding—the agent gets the same feedback you would expect from VS Code without leaving the terminal workflow. Complexity is intermediate because you need Node, a working LSP setup for your stack, and comfort with background processes.
Highlights
- Background LSP daemon so diagnostics do not block the terminal session
- Claude Code hooks run checks automatically after file edits
- JavaScript and TypeScript language-server integration
- ESLint and Prettier feedback in near realtime
- Bundle includes 3 related plugins for the client workflow
Why builders use it
Agent-made edits often compile on paper but still fail lint, format, or type rules—and you only discover that after a slow manual check.
After install, Claude-triggered edits surface language-server and linter feedback immediately so you fix issues in the same session instead of at PR time.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 51 stars, 0 votes.
FAQ
Who is eli0shin-cli-lsp-client for?
It is for indie developers who code with Claude Code on JavaScript or TypeScript and want automatic ESLint, Prettier, and LSP checks after every agent edit.
When should I use eli0shin-cli-lsp-client?
Use it when you are actively building or refactoring TS/JS in Claude Code and tired of discovering lint and type errors only when you run checks manually.
How do I add eli0shin-cli-lsp-client to my agent?
Install the cli-lsp-client CLI and daemon from the eli0shin/cli-lsp-client repository, configure your language servers, then register the plugin bundle in Claude Code per the repo’s plugin instructions.
Comments
Share how you use eli0shin-cli-lsp-client, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.