Verify
Full pre-merge verification — diagnostics, API contract, test coverage, verdictFrom its SKILL.md
npx -y skills add perilevy/lsp-intelligence --skill verifyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, as published. Nobody here has run it
Verify Changes
Full pre-commit/pre-PR verification in one command. Orchestrates diagnostics, API contract analysis, and test coverage into a single structured verdict.
Steps
-
Call
verify_changeswith the user's base branch (if specified):- If
--base <branch>provided, pass it - Otherwise, let the tool auto-detect the merge base
- If
-
Present the result in this order:
Changed files — list what was modified
Type errors — if
totalErrors > 0:- Show each file with its error count
- Show the first 3 errors per file with line and message
- Offer to run
/whyon the first error for root cause
API changes — if
apiis not null:- Show semver verdict: MAJOR / MINOR / PATCH
- If breaking > 0: list breaking changes with details
- If risky > 0: list risky changes
- Offer to run
/api-checkfor full details
Test gaps — if any
testGapshavehasTests: false:- List untested high-risk symbols with reference counts
- Offer to run
/impact <symbol>for blast radius
Verdict — show the final verdict prominently:
- "safe to merge" — all clear
- "needs attention" — breaking API changes or untested high-risk symbols
- "has errors" — type errors must be fixed first
-
If there are warnings, show them at the bottom.
-
Offer follow-up actions based on verdict:
- has errors: "Want me to fix the errors?" or
/why <file:line> - needs attention: "Want me to check the breaking changes?" or
/api-check - safe to merge: "Ready to commit?" or
/diffto review
- has errors: "Want me to fix the errors?" or
Examples
| Command | What happens |
|---|---|
/verify | Auto-detect base, check all changed files |
/verify --base main | Compare against main branch |
/verify --base develop | Compare against develop branch |