Exp Test Maintainability
dotnet/skills
Detects duplicate boilerplate, copy-paste tests, and structural maintainability issues across .NET test suites.
Full three-layer verification after any change — LSP diagnostics + compiler build + test suite, ranked by severity.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-verify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "lsp-verify" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-verify into .claude/skills/lsp-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-verify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-verifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/lsp-verify .agents/skills/lsp-verify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lsp-verify" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-verify into .agents/skills/lsp-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-verify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/lsp-verify .cursor/skills/lsp-verify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lsp-verify" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-verify into .cursor/skills/lsp-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-verify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/blackwell-systems/agent-lsp.git --path skills/lsp-verify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/lsp-verify .gemini/skills/lsp-verify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lsp-verify" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-verify into .gemini/skills/lsp-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-verify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install blackwell-systems/agent-lsp lsp-verifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add blackwell-systems/agent-lsp --skill lsp-verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/lsp-verify .github/skills/lsp-verify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lsp-verify" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-verify into .github/skills/lsp-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-verify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/lsp-verify .opencode/skills/lsp-verify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lsp-verify" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-verify into .opencode/skills/lsp-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-verify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
lsp-verifyFull 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. 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.
Read from SKILL.md and the folder at commit 38ca488. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
mcp__lsp__get_diagnosticsmcp__lsp__run_buildmcp__lsp__run_testsmcp__lsp__get_tests_for_filemcp__lsp__suggest_fixesmcp__lsp__format_documentmcp__lsp__apply_editFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
goFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)
From compatibility in the SKILL.md frontmatter.
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.
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.
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.
The full file from blackwell-systems/agent-lsp at commit 38ca488, republished under its MIT licence (© blackwell-systems). 633 words, ~2,049 tokens.
.claude/skills/lsp-verify/SKILL.md (or your agent's skills folder).Requires the agent-lsp MCP server.
Run this skill after any significant change to verify correctness at every level:
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 diagnosticschanged_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.
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.
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.
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:
grep -E "^(FAIL|--- FAIL)" <output_file>Or scope tests to the correlated test files from the pre-step to avoid the size issue entirely:
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.
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]| Layer | Errors | Warnings |
|---|---|---|
| LSP Diagnostics | Blocking | Advisory |
| Build | All blocking | N/A |
| Tests | All blocking | N/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.
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.
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
Just SKILL.md in skills/lsp-verify of blackwell-systems/agent-lsp.
Open the folder on GitHubat commit 38ca488
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lsp Verify this skillblackwell-systems/agent-lsp | 160 | — | ~2k | Automated safety check: Pass | MIT | |
| Exp Test Maintainabilitydotnet/skills | 5.6k | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Feature ContractFastLED/FastLED | 7.5k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Interval Difference AnalyzerArabelaTso/Skills-4-SE | 253 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Code SolvingHoangTheQuyen/think-better | 122 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Improve Codebase ArchitectureTwiTech-LAB/devchain | 101 | — | ~3k | Automated safety check: Pass | MIT |
dotnet/skills
Detects duplicate boilerplate, copy-paste tests, and structural maintainability issues across .NET test suites.
FastLED/FastLED
Generate a structured implementation contract before making any code changes to FastLED.
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.
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.
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…
npc-live/clawfirm
Software development workflow dispatcher. An agent skill from npc-live/clawfirm.
blackwell-systems/agent-lsp
Enumerate exported symbols in a file and surface those with zero references across the workspace.
blackwell-systems/agent-lsp
Safe workflow for editing exported symbols or public APIs. An agent skill from blackwell-systems/agent-lsp.
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.
blackwell-systems/agent-lsp
Trigger language server code generation — implement interface stubs, generate test skeletons, add missing methods, generate mock types.
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.
blackwell-systems/agent-lsp
Two-phase safe rename across the entire workspace. An agent skill from blackwell-systems/agent-lsp.
Categories
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.
Lsp Verify fits situations like: tasks that involve Test generation; tasks that involve Refactoring.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.