lsp-verify

Verify LSP diagnostics, build, and tests after code edits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After edits, developers risk introducing regressions across language tooling. This Skill provides an end-to-end verification loop to catch issues in LSP diagnostics, compilation, and tests.

Core Features & Use Cases

  • Three-layer verification: LSP diagnostics, build, and tests, plus optional post-fix formatting.
  • Pre-step support: test correlation to map changes to tests for targeted analysis.
  • Post-verify actions: surface and apply code actions to fix issues and re-check.

Quick Start

Run the three verification layers after making changes to ensure the codebase remains healthy.

Frequently Asked Questions about lsp-verify

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

FAQPage Schema
How do I verify LSP diagnostics after making code edits?

Verify LSP diagnostics after edits by running a three-layer regression check that analyzes language-server intelligence, build compilation, and test suite integrity to catch introduced issues.

What is the best way to run regression testing for language server protocol changes in CI?

Regression testing for LSP changes in CI uses a verification loop that maps edits to correlated tests, runs diagnostics and builds, and applies post-fix code actions to ensure workspace health.

Can I automatically apply code actions to fix build failures after running tests?

Yes, you can automatically apply code actions to fix build failures after running tests, as the post-verification flow surfaces and applies fixes before re-checking the workspace.

How does test correlation work before running codebase diagnostics?

Test correlation works as a pre-step that maps specific code changes to targeted tests, enabling focused analysis and preventing unnecessary full test suite execution during verification.

Do I need an integrated MCP server to run build and test verification?

Yes, an integrated MCP server and configured workspace are required, as the verification flow relies on them to execute the three layers and apply post-verify formatting.