Api check
Check for breaking API changes — what exports changed, who consumes them, and semver impactFrom its SKILL.md
npx -y skills add perilevy/lsp-intelligence --skill api-checkAssembled 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.2 KB, as published. Nobody here has run it
API Guard
Check the public API surface for breaking changes before merging.
Steps
-
Parse the user's input:
- If
--base <branch>: use that as the comparison base - If
--scope all: check all files, not just changed ones - Default: changed files only, base auto-detected from main/master
- If
-
Run
api_guardwith the parsed arguments -
Present the result:
- Semver verdict: MAJOR (breaking), MINOR (additive), PATCH (internal)
- Breaking changes: list with structural diffs and consumer counts
- Risky changes: changes that might break consumers
- Safe changes: additive or internal-only
-
For each breaking change, highlight:
- What exactly changed (enum member added, param now required, etc.)
- How many cross-package consumers are affected
- Sample consumer files
-
If breaking changes exist:
- Suggest running
/impacton the most impactful symbol - Ask if the breaking change is intentional
- Offer to run
/checkon consumer files to verify they compile
- Suggest running