diagnostics

Name: diagnostics
Availability: InStock
Author: samibrahmi

Retrieve LSP diagnostics per file and suggest rollback checkpoints.

Updated Apr 18, 2026

Search Tags:#debugging #rollback #diagnostics #lsp #code-quality #version-control

Ready to run

npx skills add https://github.com/samibrahmi/instanotes-api --skill diagnostics-samibrahmi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/samibrahmi/instanotes-api/tree/main/newcontent/skills/diagnostics
Command: npx skills add https://github.com/samibrahmi/instanotes-api --skill diagnostics-samibrahmi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers identify and surface LSP diagnostics to fix static code issues and provides a safe path to revert changes when needed.

Core Features & Use Cases

Retrieve LSP diagnostics (syntax errors, type errors, and code issues) per file or project.
Suggest rollback to a previous checkpoint when changes cause widespread issues.
Use after refactoring or dependency changes to validate code health and guide undo actions.

Quick Start

Run getLatestLspDiagnostics to fetch current issues and then, if needed, invoke suggestRollback to restore a previous checkpoint.

Frequently Asked Questions about diagnostics

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

FAQPage Schema

How do I check LSP diagnostics to debug static code issues after refactoring?▼

You can retrieve LSP diagnostics per file to identify syntax and type errors after refactoring. This surfaces static code issues to help you debug changes before deciding if a rollback to a previous checkpoint is necessary.

What is the best way to rollback code changes when new imports cause widespread errors?▼

When imports cause widespread errors, use a rollback suggestion mechanism. It guides you toward previous checkpoints to restore code health without performing the rollback automatically, ensuring safe version control recovery.

Can I retrieve LSP diagnostics for my entire project or only per file?▼

You can retrieve LSP diagnostics for an entire project or per file. This exposes static issues like syntax and type errors, allowing you to validate overall code health after dependency changes or refactoring.

Why does my code fail silently after a refactor and how do I validate it?▼

Code may fail silently after a refactor due to hidden type or syntax issues. Validate it by fetching LSP diagnostics to surface these static code problems, which can guide you toward a safe rollback if issues are widespread.

Does this diagnostics tool automatically revert my project to a previous checkpoint?▼

No, this diagnostics tool does not automatically revert your project. It provides a rollback suggestion mechanism to guide you toward checkpoints safely, leaving the actual version control rollback action to the user.