skills.rest
naopensedoit2-design
naopensedoit2-designCOMMUNITY
Explore all skills by this author →
GitHub

diagnostics

Retrieve language server diagnostics and recommend checkpoint rollbacks for code issues.

Updated Apr 25, 2026
Search Tags:#refactoring#rollback#diagnostics#lsp#type errors#code debugging
One-click install
npx skills add https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor --skill diagnostics-naopensedoit2-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor/tree/main/.local/skills/diagnostics
Command: npx skills add https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor --skill diagnostics-naopensedoit2-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnostics helps you quickly identify static issues reported by the language server and decide when rolling back recent changes is the fastest path to restore a working project.

Core Features & Use Cases

  • LSP Diagnostics Retrieval: Pull syntax and type error reports for either a specific file or all files, so you can pinpoint what broke after edits.
  • Targeted Debugging Workflow: Focus on the file you just changed to reduce noise and speed up fixes.
  • Rollback Suggestion (Checkpoint Review): Recommend reverting to a previous state when changes cause broad failures, without automatically overwriting anything.

Quick Start

Use diagnostics to check a file for LSP errors after you refactor a large section of code, then address the reported issues or request a rollback suggestion if the breakage is widespread.

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 after refactoring?▼

To resolve type errors after refactoring, retrieve language server diagnostics scoped by file path to pinpoint syntax and import issues, then address the reported problems directly or request a rollback suggestion.

What is the best way to revert broken changes when a refactor causes widespread failures?▼

The best way to revert broken changes is to trigger a rollback suggestion workflow that prompts you to review checkpoints, restoring a working project state without automatically overwriting files.

Can I retrieve LSP diagnostics for all files instead of just one?▼

Yes, you can retrieve LSP diagnostics for all files by omitting the optional file path parameter, pulling complete syntax and type error reports to assess widespread breakage across the project.

When should I request a rollback suggestion instead of manually debugging syntax errors?▼

You should request a rollback suggestion when changes cause broad failures across multiple files, making reverting to a previous checkpoint faster than manually debugging each individual type or syntax error.

Does the rollback workflow automatically overwrite my broken code?▼

No, the rollback workflow does not automatically overwrite broken code; it provides recommendations and prompts you to view checkpoints, ensuring you maintain control over reverting changes.

Related Skills

Explore More Software Engineering Skills→
Till-Crazy-Tears-Us-ApartTill-Crazy-Tears-Us-Apart
27

file-ops

Manage file system operations with a Plan-Verify-Execute workflow.

Community
Advanced
ouzayrouzayr

diagnostics

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

Community
Intermediate
ckrono-progckrono-prog

diagnostics

Retrieve LSP diagnostics and suggest project rollback checkpoints.

Community
Intermediate
KrismithReddy12KrismithReddy12

health

Calculate a weighted 0-10 code quality score from linters and test runners.

Community
Advanced