lsp-test-correlation

> Requires the agent-lsp MCP server. # lsp-test-correlation Discover which tests cover a source file, then run only those tests. Faster than running the full suite when you've changed one or two files and want targeted feedback. ## When to use - After editing a source file: "Which tests do I need to run for this change?" - Before committing: run only the tests that cover what you touched - Debugging a failure: find which test file corresponds to a broken source file - Code review: understand what test coverage exists for a file before merging Use `/lsp-verify` instead when you want to run the full suite and check all three layers (diagnostics + build + tests). Use this skill when you want fast, scoped test execution. --- ## Workflow ### Step 1 — Find correlated test files Call `get_tests_for_file` for each edited source file: ``` mcp__lsp__get_tests_for_file({ "file_path": "/abs/path/to/source.go" }) ``` Returns the test files that correspond to the source file. For multiple edited files, call once per file. **If no test files are returned:** the source file may have no dedicated test file, or the mapping is not resolvable (e.g. integration tests in a separate directory). See Step 2 for fallback. ### Step 2 — Enumerate test functions (fallback or enrichment) If `get_tests_for_file` returns test files, use `find_symbol` to list the test functions defined in those files: ``` mcp__lsp__find_symbol({ "query": "Test" }) ``` Filter results to the correlated test fil...