diagnostics

Retrieves LSP diagnostics and suggests project rollback for debugging static errors.

Updated Mar 6, 2026

Search Tags:#static analysis #debugging #rollback #checkpoints #diagnostics #lsp #type errors

Ready to run

npx skills add https://github.com/gopaljilab/Gupta-Portfolio --skill diagnostics-gopaljilab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/gopaljilab/Gupta-Portfolio/tree/main/.local/skills/diagnostics
Command: npx skills add https://github.com/gopaljilab/Gupta-Portfolio --skill diagnostics-gopaljilab

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, and occasionally need to revert changes that broke the project. This Skill provides direct access to language server diagnostics and a guided rollback suggestion flow. ## Core Features & Use Cases - LSP Diagnostics Retrieval: Query syntax errors, type errors, and code issues for a specific file or across all files with errors. - Rollback Suggestion: Surface a "View Checkpoints" prompt when the user wants to undo changes, restore a previous version, or recover from a broken state. - Use Case: After refactoring a large module, call getLatestLspDiagnostics on the edited file to list every error with line numbers, fix them one by one, and verify the file is clean before finishing the task. ## Quick Start Check the file I just edited for any LSP errors and list them with line numbers.

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 to check all project files for LSP errors at once?▼

Call getLatestLspDiagnostics without any arguments. It returns diagnostics for every file that currently has errors, so you can see the full scope of issues across the project.

When should I check LSP diagnostics versus skip it?▼

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

Does the rollback function actually revert my code changes?▼

No, suggestRollback only displays a View Checkpoints button with your stated reason. The user must click that button to choose and restore a previous checkpoint, and the agent pauses while waiting for their response.

Why doesn't LSP diagnostics show my runtime error?▼

LSP diagnostics only cover static issues like syntax errors, type mismatches, and import problems. Runtime errors and logic bugs require logs, debugging tools, or executing the code to observe the failure.