diagnostics

Retrieve LSP diagnostics and suggest project rollback checkpoints.

Updated May 16, 2026
One-click install
npx skills add https://github.com/ckrono-prog/Kotlin-Code-Builder --skill diagnostics-ckrono-prog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/ckrono-prog/Kotlin-Code-Builder/tree/main/.local/skills/diagnostics
Command: npx skills add https://github.com/ckrono-prog/Kotlin-Code-Builder --skill diagnostics-ckrono-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides tools for debugging code issues and managing project state, helping users identify and fix static errors and manage changes effectively.

Core Features & Use Cases

  • LSP Diagnostics: Retrieve syntax errors, type errors, and code issues from language server protocols.
  • Project Rollback: Suggest rolling back to previous checkpoints to restore a working state.
  • Use Case: After a significant refactor, use this Skill to check for errors in a specific file or all files and suggest rollback if needed.

Quick Start

Run the 'diagnostics' skill to check for issues in the 'src/auth.ts' file or suggest a rollback due to unexpected 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 syntax and type errors using language server protocol diagnostics?

Language server protocol diagnostics retrieve syntax errors, type errors, and code issues by running static code analysis on specific files or entire projects. This Skill automates that retrieval to identify static errors.

Can I roll back my project to a previous checkpoint after a bad code refactor?

Yes, project rollback suggestions allow you to revert to previous checkpoints and restore a working state. This is useful after a significant refactor introduces unexpected errors across your codebase.

What do I need to run static code analysis and project state reversion?

You need file system access and Python libraries to run static code analysis and project state reversion. These dependencies enable the diagnostic services and checkpoint management functions.

When should I use LSP diagnostics instead of manually debugging code issues?

Use LSP diagnostics after a significant refactor to check for errors in specific files or all project files automatically. It provides structured error checking and rollback suggestions rather than manual inspection.

What is the best way to manage code issues and suggest project rollback?

The best way to manage code issues is running the diagnostics Skill to check for errors in specific files and suggest rolling back to previous checkpoints if unexpected errors are found.

Does this code diagnostics tool work with any programming language?

Code diagnostics work with any language supported by your configured language server protocols. The Skill retrieves syntax and type errors directly from the LSP rather than relying on language-specific rules.