lsp-verify

> Requires the agent-lsp MCP server. # lsp-verify: Three-Layer Verification ## When to Use Run this skill after any significant change to verify correctness at every level: - After editing source files (logic changes, refactors, new functions) - After merging or rebasing branches - After dependency updates or configuration changes - Before committing or pushing code ## Input - `workspace_dir` (required): absolute path to the workspace root (e.g. `/Users/you/code/myproject`) - `changed_files` (optional): list of files you edited — used for targeted diagnostics ## Execution ### Pre-step: Test correlation (when `changed_files` is provided) Before running the three layers, call `get_tests_for_file` for each changed source file to build a source → test file map: ``` mcp__lsp__get_tests_for_file({ "file_path": "<changed/source/file>" }) ``` Returns the test files that correspond to each source file. Store this map — it is used in Layer 3 to focus failure analysis. If `changed_files` is unknown, skip this step. **Run all three layers in parallel** — they are independent and do not need to be sequenced. Issue all three calls in the same message to minimize wall time. ### Layer 1: LSP Diagnostics Call `mcp__lsp__get_diagnostics` with `file_path` set to each changed file. `get_diagnostics` takes a file path, not a workspace directory. Note: requires LSP to be initialized. If not yet running, call `start_lsp` with the workspace root first. ``` mcp__lsp__get_diagnostics({...