lsp-fix-all

Apply language server quick fixes to resolve file diagnostics.

102|5|Updated Apr 6, 2026

Search Tags:#automation #diagnostics #lsp #language-server #code-actions #bulk-fix

Ready to run

npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-fix-all

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lsp-fix-all
Source: https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-fix-all
Command: npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-fix-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bulk-fix pre-existing language server diagnostics in a file by applying available quick fixes one at a time and re-collecting diagnostics between each fix.

Core Features & Use Cases

Apply quick fixes for each diagnostic one-at-a-time to resolve issues without risking cascading changes.
Re-check diagnostics after every fix to ensure stability until the file is clean or no quick-fixes remain.
Safe for non-destructive edits by skipping refactors and limiting actions to quick-fix and organizeImports.

Quick Start

Provide the path to the target file and run the lsp-fix-all skill to apply available quick fixes one by one until diagnostics are cleared.

Frequently Asked Questions about lsp-fix-all

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

FAQPage Schema

How do I bulk-fix language server diagnostics in a file automatically?▼

To bulk-fix language server diagnostics, you apply available quick fixes one at a time and re-check diagnostics after each fix until the file is clean. This ensures safe cleanup of pre-existing issues without risking cascading changes.

What is the best way to apply quick fixes for LSP diagnostics without breaking my code?▼

Applying quick fixes for LSP diagnostics one at a time, while re-checking diagnostics after each application, is the safest method. It skips structural refactors and limits actions to quick-fix and organizeImports to prevent destructive edits.

Do I need an agent-lsp MCP server to apply code actions automatically?▼

Yes, applying code actions automatically requires an agent-lsp MCP server. The workflow relies on specific MCP functions like open_document, get_diagnostics, get_code_actions, and apply_edit to operate across LSP-enabled languages.

Can I resolve all pre-existing diagnostics in LSP-enabled workflows before a code review?▼

You can resolve pre-existing diagnostics in LSP-enabled workflows by applying available quick fixes sequentially. This enables automatic cleanup of issues before edits, reviews, or refactors by enforcing quick-fix and organizeImports code actions.

What limitations exist when bulk-applying language server code actions?▼

The main limitation of bulk-applying language server code actions is that it skips structural refactors entirely. It strictly enforces quick-fix and organizeImports code actions to ensure non-destructive edits and stability between each fix.