diagnostic-scanner

Scan source projects with compilers and linters to produce prioritized diagnostic reports.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/thistleknot/skills --skill diagnostic-scanner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnostic-scanner
Source: https://github.com/thistleknot/skills/tree/main/diagnostic-scanner
Command: npx skills add https://github.com/thistleknot/skills --skill diagnostic-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

diagnostic-scanner eliminates the time-consuming work of manually running linters and compilers, interpreting noisy logs, and producing a clear, prioritized list of actionable issues.

Core Features & Use Cases

  • Language-aware tool invocation: Selects appropriate diagnostics tooling per detected language (e.g., mypy/pylint for Python, go vet/golangci-lint for Go, cargo for Rust, tsc/eslint for TS/JS).
  • Normalized error and warning extraction: Parses tool output into a consistent set of findings grouped by severity and includes file/line context.
  • Fix-prompt generation for LLM workflows: Emits a markdown report containing fix-ready context suitable for downstream automated repair.
  • Optional test compilation reporting: Supports including tests in the analysis workflow (as represented in the skill’s interface and contract).

Quick Start

Use the diagnostic-scanner skill to scan a project folder and generate a markdown diagnostic report with grouped errors and warnings ready for LLM-based fixes.

Frequently Asked Questions about diagnostic-scanner

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

FAQPage Schema
How do I turn compiler and linter output into a prioritized diagnostic report?

Generate a fix-ready markdown diagnostic report by scanning your project with language-appropriate compilers and linters. The report normalizes tool output into structured findings grouped by severity with file and line context, including embedded JSON metadata for automated repair workflows.

Can I use static analysis and linting for CI/CD gatekeeping across multiple languages?

Yes, you can use static analysis and linting for CI/CD gatekeeping across multiple languages. The scanner selects appropriate diagnostics tooling per detected language, such as mypy for Python, go vet for Go, cargo for Rust, and tsc for TypeScript.

How do I generate LLM fix prompts from code compilation errors?

Generate LLM fix prompts from code compilation errors by parsing and normalizing compiler output into a markdown report containing fix-ready context with embedded JSON metadata. This structured format provides downstream LLM workflows with the exact file and line context needed for automated repair.

Does the diagnostic scanner include test compilation results in the code quality report?

Yes, the diagnostic scanner optionally includes test compilation results in the code quality report. This feature is represented in the skill's interface and contract to support comprehensive automated code quality checks alongside standard linter and compiler findings.

What is the best way to automate code fixes from noisy linter logs?

The best way to automate code fixes from noisy linter logs is to normalize the output into structured findings grouped by severity. This eliminates manual log interpretation and produces a clear, prioritized list of actionable issues with embedded JSON metadata for automated repair.

What languages are supported by the automated code quality checks?

Automated code quality checks support Python, Go, Rust, and TypeScript/JavaScript by invoking language-appropriate diagnostics tooling such as mypy, pylint, go vet, golangci-lint, cargo, tsc, and eslint to parse output into consistent findings.