Full three-layer verification after any change — LSP diagnostics + compiler build + test suite, ranked by severity.

MITAuto-check passedDevelopment

Install Lsp Verify

skills CLI
$ npx skills add blackwell-systems/agent-lsp --skill lsp-verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install blackwell-systems/agent-lsp lsp-verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/lsp-verify .claude/skills/lsp-verify && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lsp-verify
GitHub stars
160
Token cost
~2k tokens
SKILL.md length
633 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
MIT

At a glance

Full three-layer verification after any change — LSP diagnostics + compiler build + test suite, ranked by severity.

  • Tasks that involve Test generation
  • SKILL.md covers When to Use, Input, Execution and Output Format, plus 3 more sections
  • Calls go
  • Tasks that involve Refactoring

What it does

Lsp Verify is an agent skill from blackwell-systems/agent-lsp. Full three-layer verification after any change — LSP diagnostics + compiler build + test suite, ranked by severity. Use after completing any edit, refactor, or feature to confirm nothing is broken before committing.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)

It sits in Development, covering Test generation and Refactoring. The repository describes itself as: MCP server that orchestrates language servers into agent-native workflows. 65 tools, 30 CI-verified languages. The licence is MIT.

When your agent uses it

  • Tasks that involve Test generation
  • Tasks that involve Refactoring

Example prompts

  • “/lsp-verify”

Requirements

  • Compatibility (from SKILL.md): Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)
  • Pre-approved tools (allowed-tools): mcp__lsp__get_diagnostics, mcp__lsp__run_build, mcp__lsp__run_tests, mcp__lsp__get_tests_for_file, mcp__lsp__suggest_fixes, mcp__lsp__format_document, mcp__lsp__apply_edit

What it can do on your machine

Read from SKILL.md and the folder at commit 38ca488. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • mcp__lsp__get_diagnostics
    • mcp__lsp__run_build
    • mcp__lsp__run_tests
    • mcp__lsp__get_tests_for_file
    • mcp__lsp__suggest_fixes
    • mcp__lsp__format_document
    • mcp__lsp__apply_edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)

    From compatibility in the SKILL.md frontmatter.

Context cost

Lsp Verify loads about 2k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 633 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from blackwell-systems/agent-lsp at commit 38ca488, republished under its MIT licence (© blackwell-systems). 633 words, ~2,049 tokens.

Download SKILL.mdSave it as .claude/skills/lsp-verify/SKILL.md (or your agent's skills folder).
name
lsp-verify
description
Full three-layer verification after any change — LSP diagnostics + compiler build + test suite, ranked by severity. Use after completing any edit, refactor, or feature to confirm nothing is broken before committing.
allowed-tools
mcp__lsp__get_diagnostics, mcp__lsp__run_build, mcp__lsp__run_tests, mcp__lsp__get_tests_for_file, mcp__lsp__suggest_fixes, mcp__lsp__format_document, mcp__lsp__apply_edit
compatibility
Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)
user-invocable
true
license
MIT
metadata.optional-capabilities
codeActionProvider documentFormattingProvider

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({ "file_path": "<path/to/changed/file>" })

Call once per changed file. If you don't know which files changed, call it on the primary files touched in this session. Rank results by severity: errors first, then warnings.

Layer 2: Build
mcp__lsp__run_build({ "workspace_dir": "<workspace_dir>" })

Returns { "success": bool, "errors": [...] }. A failed build means the code does not compile. Build errors are blocking — must be resolved before shipping.

Layer 3: Tests
mcp__lsp__run_tests({ "workspace_dir": "<workspace_dir>" })

Does NOT require start_lsp. Returns { "passed": bool, "failures": [...] }.

Large output warning: run_tests on large repos can return hundreds of thousands of characters and exceed the context window. If the result is saved to a file rather than returned inline, do NOT attempt to read the whole file. Instead, search it for failures:

bash
grep -E "^(FAIL|--- FAIL)" <output_file>

Or scope tests to the correlated test files from the pre-step to avoid the size issue entirely:

bash
GOWORK=off go test -count=1 -short ./internal/mypackage/... 2>&1 | grep -E "FAIL|ok"

Using test correlation: If the pre-step produced a source → test file map, cross-reference failing test names against that map. For each failure, note whether it is in a correlated test file (directly covers the changed code) or an unrelated test file (collateral failure from a shared dependency). This distinction guides where to investigate first.

Test failures are blocking — they indicate regressions or unmet contracts.

Show full SKILL.md (247 more words)Show less

Output Format

After running all three layers, produce a structured report:

## Verification Report

### Layer 1: LSP Diagnostics
[CLEAN / N errors, M warnings]

<details if N > 0 or M > 0>
Errors:
- file:line - message

Warnings:
- file:line - message
</details>

### Layer 2: Build
[PASSED / FAILED - N errors]

<details if FAILED>
- error message (file:line)
</details>

### Layer 3: Tests
[PASSED / FAILED - N failures]

<details if FAILED>
- test name: message (file:line) [correlated / unrelated]
</details>

<if test correlation map exists>
Test files covering changed source:
  changed/source/file.go → test/source_file_test.go
</if>

### Summary
Overall: CLEAN / NEEDS ATTENTION
Blocking issues: [errors that must be fixed before shipping]
  • CLEAN: no errors in any layer (warnings are advisory only)
  • NEEDS ATTENTION: one or more blocking issues found

Blocking vs Advisory

LayerErrorsWarnings
LSP DiagnosticsBlockingAdvisory
BuildAll blockingN/A
TestsAll blockingN/A

Build errors and test failures block shipping. LSP warnings and style suggestions are advisory — document them but do not treat as blockers unless they indicate logical errors.

When Verification Passes: Optional Format

If all three layers are CLEAN and changed_files is known, offer to format the changed files before committing:

mcp__lsp__format_document({ "file_path": "<changed-file>" })

Apply the returned TextEdit[] via apply_edit if non-empty. Run once per changed file. Skip if the user did not request formatting.


When Errors Are Found: Applying Code Actions

If Layer 1 returns errors, the LSP may offer quick fixes. For each error location, call suggest_fixes to surface available fixes:

mcp__lsp__suggest_fixes({
  "file_path": "<file>",
  "line": <error line>,
  "column": <error column>
})

Returns a list of available actions (e.g. "Add missing import", "Implement interface methods", "Remove unused variable"). Pick the most appropriate one and apply it:

mcp__lsp__apply_edit({
  "file_path": "<file>",
  "old_text": "<text to replace>",
  "new_text": "<replacement>"
})

Or if the code action returns a workspace_edit, pass it directly to apply_edit via the workspace_edit parameter.

After applying, re-run Layer 1 on the affected file to confirm the error is resolved before moving on. Do not apply multiple code actions in bulk without verifying each one — they may interact.

When to use: Compile errors from missing imports, unimplemented interface methods, or type mismatches often have one-click fixes available. Manual reasoning is still required for logic errors.

© blackwell-systems, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/lsp-verify of blackwell-systems/agent-lsp.

Open the folder on GitHubat commit 38ca488

Compare with similar skills

Lsp Verify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lsp Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lsp Verify this skillblackwell-systems/agent-lsp160—~2kAutomated safety check: PassMIT
Exp Test Maintainabilitydotnet/skills5.6k1 repos~2.5kAutomated safety check: PassMIT
Feature ContractFastLED/FastLED7.5k—~1.7kAutomated safety check: PassMIT
Interval Difference AnalyzerArabelaTso/Skills-4-SE253—~1.6kAutomated safety check: PassApache-2.0
Code SolvingHoangTheQuyen/think-better122—~3.7kAutomated safety check: PassMIT
Improve Codebase ArchitectureTwiTech-LAB/devchain101—~3kAutomated safety check: PassMIT

Similar skills

  • Official

    Detects duplicate boilerplate, copy-paste tests, and structural maintainability issues across .NET test suites.

    5.6k GitHub starsUsed in 1 repo~2.5k tokens
    DevelopmentAuto-check passed
  • Feature Contract

    FastLED/FastLED

    Generate a structured implementation contract before making any code changes to FastLED.

    7.5k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed
  • Interval Difference Analyzer

    ArabelaTso/Skills-4-SE

    Analyze differences in program intervals between two versions of a program (old and new) to identify added, removed, or modified intervals.

    253 GitHub stars~1.6k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Code Solving

    HoangTheQuyen/think-better

    Structured coding workflow for non-trivial code work: debug, build features, refactor, optimize, migrate and review code through 7 steps with evidence-based quality gates.

    122 GitHub stars~3.7k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Improve Codebase Architecture

    TwiTech-LAB/devchain

    Plan architecture improvements and refactoring for a codebase: scan for deepening opportunities (shallow modules, leaky seams, low-leverage interfaces), present candidates as a markdown report with…

    101 GitHub stars~3k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Dev

    npc-live/clawfirm

    Software development workflow dispatcher. An agent skill from npc-live/clawfirm.

    156 GitHub stars~642 tokensUpdated 3 mo ago
    Testing & QAAuto-check passed

More from blackwell-systems/agent-lsp

All 24 skills in this repo
  • Lsp Dead Code

    blackwell-systems/agent-lsp

    Enumerate exported symbols in a file and surface those with zero references across the workspace.

    160 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Lsp Edit Export

    blackwell-systems/agent-lsp

    Safe workflow for editing exported symbols or public APIs. An agent skill from blackwell-systems/agent-lsp.

    160 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Lsp Fix All

    blackwell-systems/agent-lsp

    Apply available quick-fix code actions for all current diagnostics in a file, one at a time with re-collection between each fix.

    160 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Lsp Generate

    blackwell-systems/agent-lsp

    Trigger language server code generation — implement interface stubs, generate test skeletons, add missing methods, generate mock types.

    160 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Lsp Impact

    blackwell-systems/agent-lsp

    Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it.

    160 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Lsp Rename

    blackwell-systems/agent-lsp

    Two-phase safe rename across the entire workspace. An agent skill from blackwell-systems/agent-lsp.

    160 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Questions about Lsp Verify

What does Lsp Verify do?

Full three-layer verification after any change — LSP diagnostics + compiler build + test suite, ranked by severity. Lsp Verify is an agent skill from blackwell-systems/agent-lsp. Full three-layer verification after any change — LSP diagnostics + compiler build + test suite, ranked by severity.

When should I use Lsp Verify?

Lsp Verify fits situations like: tasks that involve Test generation; tasks that involve Refactoring.

How do I install Lsp Verify in Claude Code?

Run `npx skills add blackwell-systems/agent-lsp --skill lsp-verify -a claude-code`. Or copy the skill folder (skills/lsp-verify in blackwell-systems/agent-lsp) into .claude/skills/lsp-verify in your project. Claude Code loads it when a task matches its description.

How do I install Lsp Verify in Codex?

Run `npx skills add blackwell-systems/agent-lsp --skill lsp-verify -a codex`. Or copy the skill folder (skills/lsp-verify in blackwell-systems/agent-lsp) into .agents/skills/lsp-verify in your project. Codex loads it when a task matches its description.

Can I use Lsp Verify in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add blackwell-systems/agent-lsp --skill lsp-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lsp-verify, .gemini/skills/lsp-verify, .github/skills/lsp-verify and .opencode/skills/lsp-verify in your project.

What does Lsp Verify need to run?

Going by SKILL.md and its folder, Lsp Verify needs the command-line tools its instructions call (go). Its frontmatter pre-approves these tools: mcp__lsp__get_diagnostics, mcp__lsp__run_build, mcp__lsp__run_tests, mcp__lsp__get_tests_for_file, mcp__lsp__suggest_fixes, mcp__lsp__format_document, mcp__lsp__apply_edit. Compatibility (from SKILL.md): Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp).

Does Lsp Verify access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Lsp Verify safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lsp Verify use?

Lsp Verify is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lsp Verify use?

About 2k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Lsp Verify?

Skills that share tags, products or a category with Lsp Verify: Exp Test Maintainability (dotnet/skills, 5.6k stars), Feature Contract (FastLED/FastLED, 7.5k stars), Interval Difference Analyzer (ArabelaTso/Skills-4-SE, 253 stars) and Code Solving (HoangTheQuyen/think-better, 122 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lsp Verify?

blackwell-systems (a GitHub user) maintains it in blackwell-systems/agent-lsp, which has 160 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 10, 2026.

Source: blackwell-systems/agent-lsp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.