diagnostics

Detect static code errors and recommend checkpoint-based rollback guidance.

Updated Jun 20, 2026

Search Tags:#debugging #rollback #diagnostics #lsp #syntax errors #type errors

Ready to run

npx skills add https://github.com/4tie/fortiesr --skill diagnostics-4tie

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/4tie/fortiesr/tree/main/.local/skills/diagnostics
Command: npx skills add https://github.com/4tie/fortiesr --skill diagnostics-4tie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly identify static code issues and decide when a rollback is the safest path after edits or refactors.

Core Features & Use Cases

LSP Diagnostics Review: Checks files or the whole workspace for syntax errors, type errors, and import problems.
Targeted Debugging: Focuses on the file you just changed when a specific issue needs verification.
Rollback Guidance: Suggests a checkpoint-based revert when changes have broken the project or the user wants to undo work.
Use Case: After a large refactor, use it to scan for unresolved diagnostics before handing the code back.

Quick Start

Ask the diagnostics skill to check the latest LSP errors for the file you just edited and tell you whether a rollback is recommended.

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 after a large code refactor?▼

To check for syntax and type errors after a refactor, review LSP diagnostics across the workspace or targeted files. This catches import issues and type-checking failures introduced by recent changes.

What is the best way to undo recent code changes that destabilized my project?▼

The best way to undo destabilizing code changes is to use checkpoint-based rollback guidance. This safely reverts your project to a stable state when new imports or refactors break the build.

How do I review LSP diagnostics for a specific file I just changed?▼

You can review LSP diagnostics for a specific changed file by running a targeted debugging check. This focuses error detection on the exact file needing verification after an edit.

Does rollback guidance work for type-checking failures caused by new imports?▼

Yes, rollback guidance works for type-checking failures caused by new imports. When new imports destabilize the project, a checkpoint-based revert is recommended to safely recover the codebase.

When should I avoid rolling back code and try to fix errors instead?▼

You should avoid rolling back code when static code errors are isolated and easily fixable. Rollback is recommended primarily when recent changes broadly destabilize the project or cause widespread import failures.

Can I detect import problems across my whole workspace or just individual files?▼

You can detect import problems across your whole workspace or individual files. LSP diagnostics review supports both full workspace scans and targeted checks on specific recently changed files.