diagnostics

Retrieve LSP diagnostics for static code errors and suggest project rollbacks.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/BasitShafiq/personal --skill diagnostics-basitshafiq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/BasitShafiq/personal/tree/main/.local/skills/diagnostics
Command: npx skills add https://github.com/BasitShafiq/personal --skill diagnostics-basitshafiq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers identify and fix code errors using Language Server Protocol (LSP) diagnostics and provides a mechanism to revert project changes when necessary.

Core Features & Use Cases

  • LSP Diagnostics: Retrieves syntax, type, and other static code errors detected by the LSP.
  • Project Rollback Suggestion: Offers to guide users through reverting to a previous stable state.
  • Use Case: After a large code refactor, use this Skill to check for any introduced errors and, if the user is unhappy with the changes, suggest rolling back to a previous version.

Quick Start

Use the diagnostics skill to check for any errors in the file 'src/app.js'.

Frequently Asked Questions about diagnostics

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

FAQPage Schema
How do I check for static code errors using LSP diagnostics?

LSP diagnostics identify static code errors by retrieving syntax and type issues detected by the Language Server Protocol. The Skill reports these problems directly, helping developers pinpoint issues introduced during refactoring without manual review.

Can I rollback project changes to a previous checkpoint after a bad refactor?

Yes, you can rollback project changes to a previous checkpoint after a bad refactor. The Skill facilitates project state management by suggesting rollbacks based on user-defined reasons, allowing you to revert unintended code modifications and restore a stable state.

What is the best way to revert unintended code modifications in version control?

The best way to revert unintended code modifications is to use the project rollback suggestion feature. It guides you through reverting to a previous stable state by specifying a reason for the rollback, effectively undoing unwanted changes while maintaining project state integrity.

Does this tool find syntax and type issues without running the code?

Yes, this tool finds syntax and type issues without running the code. It accesses Language Server Protocol diagnostics to identify and report static code errors, meaning it analyzes the code structure statically rather than executing it to discover problems.

When should I use a rollback suggestion for debugging static errors?

You should use a rollback suggestion for debugging static errors when you are unhappy with recent changes or a large refactor introduces complex issues. It helps revert to a previous version, bypassing the need to manually fix multiple newly introduced errors.