diagnostics

Retrieve LSP diagnostics for files and propose rollback suggestions.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Soufianouassif/Web3-Presale-Platform --skill diagnostics-soufianouassif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/Soufianouassif/Web3-Presale-Platform/tree/main/.local/skills/diagnostics
Command: npx skills add https://github.com/Soufianouassif/Web3-Presale-Platform --skill diagnostics-soufianouassif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps identify and surface LSP diagnostics to debug static code errors and support safe rollback planning.

Core Features & Use Cases

  • Retrieve LSP diagnostics for a specific file or the entire project to surface syntax, type, and import issues.
  • Propose rollback suggestions when changes introduce instability, enabling quick restoration of a working state.
  • Guide debugging after large refactors or user-reported errors by surfacing actionable insights and recovery options.

Quick Start

Inspect current LSP diagnostics for a file or project and initiate a rollback suggestion if issues are detected.

Frequently Asked Questions about diagnostics

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

FAQPage Schema
How do I use LSP diagnostics to debug static code errors after a refactor?

Use LSP diagnostics to identify and surface static code errors during debugging after a major refactor. Apply this process when users report errors or after large changes to guide your rollback and recovery decisions.

What is the best way to roll back code changes that introduced instability?

The best way to roll back unstable code changes is to generate rollback suggestions that enable quick restoration of a working state. This helps guide debugging after large refactors by surfacing actionable recovery options.

Can I check project state and code quality across an entire project or just single files?

You can inspect LSP diagnostics for both a specific file and the entire project. This surfaces syntax, type, and import issues across the project state to guide debugging and rollback decisions.

When should I run LSP diagnostics to check for syntax and import issues?

Run LSP diagnostics after major changes, large refactors, or when users report errors. This surfaces actionable insights and recovery options to guide debugging and support safe rollback planning.

Do I need any external dependencies to surface static errors and suggest rollbacks?

No external dependencies are required to surface static errors and suggest rollbacks. The process implements getLatestLspDiagnostics and suggestRollback with structured outputs and frontmatter-based discovery.