diagnostics

Name: diagnostics
Availability: InStock
Author: not-subhu

Retrieve Language Server Protocol diagnostics for syntax and type errors.

Updated Jun 30, 2026

Search Tags:#project management #rollback #diagnostics #LSP #code debugging

Ready to run

npx skills add https://github.com/not-subhu/screech --skill diagnostics-not-subhu

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill assists in identifying and managing code issues, providing a streamlined approach to debugging and project state management.

Core Features & Use Cases

LSP Diagnostics: Retrieve syntax errors, type errors, and code issues from LSP.
Project Rollback: Suggest rolling back to a previous checkpoint for error correction.
Use Case: When refactoring a large portion of code, this Skill can help by checking for errors, suggesting rollbacks if needed, and aiding in debugging static errors.

Quick Start

To check for errors in a specific file, use: getLatestLspDiagnostics(filePath="path/to/file").

Frequently Asked Questions about diagnostics

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

FAQPage Schema

How do I check for syntax and type errors using LSP diagnostics?▼

You can check for LSP diagnostics by retrieving the latest syntax and type errors for a specific file path. This provides code debugging assistance by identifying static issues directly from the Language Server Protocol.

What is the best way to undo code changes after a large refactoring?▼

The best way to undo code changes after large refactoring is a project rollback. This suggests rolling back to a previous checkpoint for error correction, effectively managing the project state to restore stable code.

Do I need a language server environment to run code debugging diagnostics?▼

Yes, you need a language server environment to run code debugging diagnostics. The Skill must be executed within an environment that has access to the project's language server and relevant diagnostics data to function properly.

Can I retrieve code issues for a specific file path?▼

Yes, you can retrieve code issues for a specific file path by querying the latest LSP diagnostics. This targets the exact file you are debugging, returning syntax errors, type errors, and other code issues directly.

When should I roll back my project state instead of fixing static errors manually?▼

You should roll back your project state when refactoring introduces overwhelming static errors. Suggesting a rollback to a previous checkpoint provides a faster path to error correction than manually resolving numerous syntax or type issues.