lsp-inspect

> Requires the agent-lsp MCP server. # lsp-inspect Full code quality audit for a file, package, or directory. Combines LSP batch analysis (`blast_radius`) with targeted per-symbol checks and LLM-driven heuristic analysis. Produces a severity-tiered findings report with confidence tiers and fix suggestions. ## When to Use - Auditing a package before a release or major refactor - Finding dead code, untested exports, and error handling gaps in unfamiliar code - Reviewing code quality of an external codebase for contribution opportunities - Pre-merge quality gate on a set of changed files - Batch inspection of an entire directory with ranked output - Comparing branch changes against main to find newly introduced issues ## Input ``` /lsp-inspect <target> [--checks <type1>,<type2>] [--json] [--top N] [--diff] ``` **Target** can be: - A file path: `/lsp-inspect src/handlers/auth.go` - A directory/package: `/lsp-inspect internal/runnables/` - Multiple targets: `/lsp-inspect pkg/a.go pkg/b.go` **Directory detection:** When target is a directory, walk all `.go`, `.ts`, `.py` files in it recursively. Produce a ranked report: "Top N findings sorted by severity then blast radius." **Flags:** - `--checks <type1>,<type2>`: only run listed check types (default: all applicable) - `--json`: emit structured JSON instead of markdown - `--top N`: Maximum findings to report (default 20). Only applies to directory/batch mode. - `--diff`: Only inspect files changed vs main branch. Filter fi...