skills.rest
BotchaVarun
BotchaVarunCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

diagnostics

Retrieve LSP diagnostics and suggest project rollback to previous checkpoints.

Updated Mar 8, 2026
Search Tags:#static analysis#debugging#rollback#checkpoints#diagnostics#lsp#type errors
One-click install
npx skills add https://github.com/BotchaVarun/EduBot --skill diagnostics-botchavarun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/BotchaVarun/EduBot/tree/main/.local/skills/diagnostics
Command: npx skills add https://github.com/BotchaVarun/EduBot --skill diagnostics-botchavarun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After making code changes, developers need a fast way to detect syntax errors, type errors, and import issues across files, and a safe path to revert when changes break the project. ## Core Features & Use Cases - LSP Diagnostics Retrieval: Query language server diagnostics for a specific file or all files with errors, returning line numbers and error messages. - Rollback Suggestion: Prompt the user with a View Checkpoints button to restore a previous working state when changes cause widespread failures. - Use Case: After refactoring a large module, call getLatestLspDiagnostics on the edited file to list every type error, fix them one by one, and if the user says "everything is broken", call suggestRollback to offer a checkpoint restore. ## Quick Start Check the file I just edited for any LSP errors and list each issue with its line number.

Frequently Asked Questions about diagnostics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for type errors after editing a file?▼

Call getLatestLspDiagnostics with the filePath parameter set to the edited file. It returns a dictionary mapping file paths to error lists, each with line numbers and messages you can iterate over and fix.

How do I check all project files for LSP errors at once?▼

Call getLatestLspDiagnostics without any arguments. It returns diagnostics for every file with errors, so you can count affected files and loop through each error entry.

When should I check LSP diagnostics versus skipping it?▼

Check LSP after refactoring more than 100 lines, adding imports or dependencies, or when the user reports errors. Skip it for changes under 10 lines, comment edits, or runtime bugs that the language server cannot detect.

Can LSP diagnostics find runtime errors or logic bugs?▼

No. LSP diagnostics only surface static issues like syntax errors, type mismatches, and import problems. Runtime errors and logic bugs require logs, debugging tools, or test execution instead.

Does suggestRollback actually revert my code changes?▼

No. suggestRollback only displays a View Checkpoints button with your reason and pauses the agent. The user must click the button and choose a checkpoint to perform the actual rollback.

Related Skills

Explore More Software Engineering Skills→
1uc4sm4theus1uc4sm4theus
20

diagnostics

Retrieve language server diagnostics to identify static code errors and manage rollback checkpoints.

Community
Intermediate
eumemiceumemic

test

Execute automated and manual tests and report go/no-go results.

Community
Intermediate
anxiety135790anxiety135790

requesting-code-review

Scan git diffs for security risks and run baseline-aware tests before commit.

Community
Advanced
shakhovskiya-createshakhovskiya-create

code-audit

Aggregate SAST results for Python, JS/TS, and Go codebases.

Community
Intermediate