diagnostics

Retrieve LSP diagnostics and suggest rollback points for code regressions.

18|4|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/El3tar-cmd/DevHive-Cli --skill diagnostics-el3tar-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/El3tar-cmd/DevHive-Cli/tree/main/skills/diagnostics
Command: npx skills add https://github.com/El3tar-cmd/DevHive-Cli --skill diagnostics-el3tar-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface LSP diagnostics to guide debugging and provide safe rollback suggestions when changes introduce regressions, helping teams maintain code quality.

Core Features & Use Cases

  • Retrieve latest LSP diagnostics for a single file or entire project.
  • Suggest rollback points after risky refactors or large changes.
  • Provide a clear workflow to inspect diagnostics and restore a stable state.

Quick Start

Use the skill to run an LSP diagnostics pass on the target file or project and surface syntax and type errors.

Frequently Asked Questions about diagnostics

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

FAQPage Schema
How do I check for code regressions after a large refactor?

To check for code regressions after a large refactor, run an LSP diagnostics pass to surface syntax and type errors across your codebase, guiding debugging and suggesting rollback points if issues are detected.

What is the best way to revert code changes that introduced syntax errors?

The best way to revert code changes that introduced syntax errors is to view checkpoints prompted by diagnostic workflows, allowing you to inspect rollback points and restore a stable working version of your file or project.

Can LSP diagnostics detect type errors across an entire project?

Yes, LSP diagnostics can detect type errors across an entire project by retrieving the latest diagnostics for affected files, helping surface code issues and prevent unnoticed regressions during large changes.

How do I get rollback suggestions after risky edits in version control?

To get rollback suggestions after risky edits in version control, trigger diagnostic retrieval workflows that identify regressions and prompt you to view checkpoints to restore a previously working version.

When do I need to run diagnostics on my codebase?

You need to run diagnostics on your codebase when applying edits that affect syntax, types, or imports, ensuring you catch regressions early and receive rollback guidance for restoring a stable state.

Does running diagnostics require any specific dependencies or components?

No specific dependencies or components are required to run diagnostics, as the skill operates independently to retrieve LSP diagnostics and provide rollback workflows for your codebase.