diagnostics

Retrieve LSP diagnostics and propose rollback checkpoints for project changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tools for debugging code issues and managing project state.

Core Features & Use Cases

  • Access the latest LSP diagnostics across a project to identify syntax, type, or import issues.
  • Suggest safe rollback points when changes cause widespread errors or regressions.
  • Guide users on when to check diagnostics vs. when to revert changes.

Quick Start

Run getLatestLspDiagnostics to fetch current diagnostics for a specific file or for all files with errors.

Frequently Asked Questions about diagnostics

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

FAQPage Schema
How do I get LSP diagnostics for a specific file to debug syntax and import errors?

To get LSP diagnostics for a specific file, you can retrieve the latest diagnostics to identify syntax, type, or import issues. Running getLatestLspDiagnostics fetches current diagnostics for a targeted file or for all files with errors.

When should I roll back code changes instead of trying to fix the errors?

You should roll back code changes when modifications cause widespread errors or regressions. The suggestRollback function proposes safe rollback checkpoints to help you revert changes when static analysis shows widespread issues.

Can I check static analysis errors across my entire project at once?

Yes, you can check static analysis errors across your entire project. The getLatestLspDiagnostics function fetches current diagnostics for all files with errors, allowing you to identify syntax, type, or import issues project-wide.

What is the best way to revert changes after a regression introduces code quality issues?

The best way to revert changes after a regression is to use suggestRollback. It proposes safe rollback points and checkpoints to help you revert changes when modifications introduce widespread code quality issues or static errors.

Do I need a specific debugging workflow to manage project state and static errors?

You need a debugging workflow that checks diagnostics before reverting changes. This workflow guides you on when to check LSP diagnostics versus when to revert changes, managing project state by identifying syntax, type, or import issues.