diagnostics

Retrieve LSP diagnostics and suggest rollback options without automatic execution.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/offers-png/one-time-checkout --skill diagnostics-offers-png
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/offers-png/one-time-checkout/tree/main/.local/skills/diagnostics
Command: npx skills add https://github.com/offers-png/one-time-checkout --skill diagnostics-offers-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Access LSP diagnostics to identify static code issues and guide safe rollback planning to revert changes.

Core Features & Use Cases

  • Retrieve the latest LSP diagnostics for a specific file or the entire project.
  • Propose safe rollback options without performing the rollback automatically.
  • Provide guidance for debugging static errors detected by the language server.

Quick Start

Run getLatestLspDiagnostics to fetch current diagnostics, and if issues are detected, consider suggestRollback with a clear reason to explore reverting.

Frequently Asked Questions about diagnostics

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

FAQPage Schema
How do I retrieve LSP diagnostics to debug static errors in my project?

You can retrieve LSP diagnostics by running getLatestLspDiagnostics to fetch current static code issues for a specific file or the entire project. This identifies code-quality problems detected by the language server.

How do I plan a safe rollback after refactoring introduces static errors?

To plan a safe rollback after refactoring, use suggestRollback with a clear reason to explore reverting changes. This proposes rollback options to resolve static errors without performing the rollback automatically.

Can I check LSP diagnostics for a single file instead of the whole project?

Yes, you can check LSP diagnostics for a single file. The getLatestLspDiagnostics function supports both per-file and global diagnostics retrieval to help you isolate static errors during debugging.

What is the best way to revert code changes when static issues appear after edits?

The best way to revert code changes when static issues appear is to fetch LSP diagnostics first, then call suggestRollback with a clear reason. This provides safe rollback planning without executing automatic reverts.

Does the rollback suggestion execute automatically when static errors are detected?

No, the rollback suggestion does not execute automatically when static errors are detected. The suggestRollback function only proposes safe rollback options, ensuring you maintain control over reverting changes.