Check
Run type checking on files — catch errors immediately after editsFrom its SKILL.md
npx -y skills add perilevy/lsp-intelligence --skill 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
0.9 KB, as published. Nobody here has run it
Type Check
Check for type errors after edits and explain any issues found.
Steps
- Determine which files to check:
- If the user specified file paths, use those
- Otherwise, run
git diff --name-onlyin the workspace to find changed TypeScript files - If no git changes found, ask the user which files to check
- Run
live_diagnosticson each file - For each file:
- If clean: report "no errors"
- If errors found: run
explain_erroron each error location to get actionable context
- Present a summary:
- Clean files: list them briefly
- Files with errors: show each error with the explanation and suggested fix
- Total: "X files checked, Y errors found"
- If errors were found, offer to fix them