lean-diagnostics

Parse and triage Lean 4 build diagnostics to identify failing components and root causes.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/my04337/shapez2-in-lean --skill lean-diagnostics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lean-diagnostics
Source: https://github.com/my04337/shapez2-in-lean/tree/main/.github/skills/lean-diagnostics
Command: npx skills add https://github.com/my04337/shapez2-in-lean --skill lean-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parse and triage Lean 4 build diagnostics to quickly identify failures, prioritize fixes, and surface actionable insights.

Core Features & Use Cases

  • Triage Lean 4 build errors and warnings from lake, lean tool outputs, and CI logs.
  • Detect and surface 'sorry' proofs for attention, along with dependency-related failures.
  • Generate prioritized action lists and diagnostics summaries to guide developers during Lean project builds.

Quick Start

Analyze your Lean 4 build output to identify errors, triage warnings, and surface 'sorry' proofs for focused fixes.

Frequently Asked Questions about lean-diagnostics

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

FAQPage Schema
How do I triage Lean 4 build errors and warnings from CI logs?▼

To triage Lean 4 build errors, you can parse outputs from lake, lean tool outputs, and CI logs to classify errors and warnings, generating a prioritized action list for focused fixes.

What is the best way to detect 'sorry' proofs in Lean 4 projects?▼

Detecting 'sorry' proofs in Lean 4 projects involves parsing build diagnostics with specific flags to surface incomplete proofs, ensuring developers can prioritize and address dependency-related failures quickly.

Can I parse local development build outputs to identify failing Lean components?▼

Yes, you can parse local development build outputs to identify failing Lean components and root causes, applying diagnostic triage to surface prioritized actions for your Lean projects.

How do I generate a diagnostics summary for Lean project builds?▼

You generate a diagnostics summary for Lean project builds by parsing build outputs, classifying the extracted errors and warnings, and surfacing actionable insights to guide developers.

Does this approach work for classifying dependency-related failures in Lean 4?▼

Yes, this approach works for classifying dependency-related failures in Lean 4 by parsing and triaging build diagnostics to identify root causes and surface prioritized actions.