lean-doc-improvement

Triage Lean-derived updates and generate patches for documentation handbooks.

2|Updated May 26, 2026
One-click install
npx skills add https://github.com/r-irbe/proof-skills --skill lean-doc-improvement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lean-doc-improvement
Source: https://github.com/r-irbe/proof-skills/tree/main/skills/lean-doc-improvement
Command: npx skills add https://github.com/r-irbe/proof-skills --skill lean-doc-improvement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Keeps Lean-related documentation and handbooks in sync with new formalization results, corrections, and insights discovered during Lean4 work.

Core Features & Use Cases

  • Triage Lean-derived updates to the documentation handbook, papers, and handbooks.
  • Generate patches and patch-notes, map changes to the appropriate sections in the references handbook, and coordinate handoffs to downstream skills.
  • Use case: when a Lean proof reveals a missing hypothesis that affects an appendix table, automatically propagate the update to the relevant document.

Quick Start

Update the lean-doc handbook to reflect the latest Lean formalization results.

Frequently Asked Questions about lean-doc-improvement

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

FAQPage Schema
How do I update documentation when Lean formalization reveals new corrections?

To update documentation from Lean formalization, triage the new insights, generate patches, map them to the appropriate handbook sections, and coordinate downstream handoffs with safety STOP checks to keep proofs and docs in sync.

What is the workflow for syncing a Lean proof handbook with new results?

The Lean proof handbook workflow involves triaging formalization updates, creating patch notes, mapping changes to reference sections, and executing downstream handoffs to ensure documentation reflects the latest Lean4 work.

Can I use this to update technical reports and papers, or only handbooks?

You can use this for papers, technical reports, and handbooks. It triages Lean-derived updates and propagates them to the relevant document whenever formalization yields new insights, corrections, or metrics.

What's the best way to propagate a missing hypothesis from a Lean proof to an appendix table?

The best way to propagate a missing hypothesis is using the patch-generation workflow, which maps the Lean formalization correction directly to the affected appendix table in the references handbook.

When should I use safety STOP checks during Lean documentation updates?

You should use safety STOP checks during the patch-generation workflow before coordinating handoffs to downstream skills, ensuring that section mapping and Lean-derived updates are verified before propagation.