diagnostics

Retrieves LSP diagnostics for syntax, type, and import errors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers identify and fix static code errors, and provides a mechanism to revert project changes when issues arise.

Core Features & Use Cases

  • LSP Diagnostics: Retrieves syntax, type, and import errors detected by the Language Server Protocol.
  • Project Rollback: Suggests reverting to a previous stable version of the codebase.
  • Use Case: After making significant code modifications, you can use this skill to check for any new errors introduced and, if the code becomes unstable, easily roll back to a known good state.

Quick Start

Use the diagnostics skill to check for errors in the file 'src/utils.ts'.

Frequently Asked Questions about diagnostics

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

FAQPage Schema
How do I check for TypeScript and import errors in my project files?

To check for TypeScript and import errors, access Language Server Protocol (LSP) diagnostics to identify static code issues. This retrieves syntax, type, and import errors detected by the LSP within specified files or across the project.

What is the best way to revert code changes after introducing instability?

The best way to revert code changes is using a project rollback mechanism to revert to a previous checkpoint. You provide a user-defined reason, and the system suggests reverting the project to a known good state.

How do LSP diagnostics identify static code errors in a codebase?

LSP diagnostics identify static code errors by analyzing files for syntax, type, and import issues. The Language Server Protocol processes the code to detect these errors, providing detailed reports for debugging and quality assurance.

Can I use this to debug syntax issues across my entire project?

Yes, you can debug syntax issues across your entire project. The diagnostics retrieve static code errors detected by the Language Server Protocol across the project, allowing you to identify and fix widespread syntax, type, and import problems.

What should I do if my code becomes unstable after significant modifications?

If your code becomes unstable after significant modifications, use the project rollback feature to revert to a previous stable version. This suggests reverting project changes to a previous checkpoint based on your user-defined reasons.