proof-review-checklist

Review Lean 4 proof files for quality, cleanup, and coding standards.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/fmhall/lean-png --skill proof-review-checklist-fmhall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proof-review-checklist
Source: https://github.com/fmhall/lean-png/tree/main/.claude/skills/proof-review-checklist
Command: npx skills add https://github.com/fmhall/lean-png --skill proof-review-checklist-fmhall

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining high-quality Lean proofs by providing a comprehensive checklist for review, ensuring thoroughness and consistency.

Core Features & Use Cases

  • Proof Quality Assurance: Offers a systematic approach to reviewing Lean proofs, ensuring they meet established quality standards.
  • Automated Metrics Collection: Tracks metrics like bare simp counts before and after changes, aiding in the assessment of proof efficiency.
  • Mechanical Cleanup Steps: Provides step-by-step instructions for mechanical proof cleanup, such as merging consecutive rw calls and removing dead have bindings.

Quick Start

Run the proof-review-checklist skill on your Lean proof file to start the review process.

Frequently Asked Questions about proof-review-checklist

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

FAQPage Schema
How do I review Lean 4 proofs for quality and coding standard adherence?

Review Lean 4 proofs by running an automated checklist that analyzes proof files for quality, mechanical cleanup opportunities, and adherence to established coding standards.

What mechanical cleanup steps can I automate when reviewing Lean proofs?

Automate Lean proof cleanup through steps like merging consecutive `rw` calls and removing dead `have` bindings to ensure your proofs meet structural quality standards.

Can I track proof efficiency metrics like bare simp counts before and after changes?

Yes, automated metrics collection tracks bare simp counts before and after changes, aiding in the assessment of proof efficiency and helping measure the impact of your modifications.

Does this proof review checklist require any specific dependencies or environment setup?

No specific dependencies are required; the skill utilizes shell commands and Lean proof tactics to analyze and improve proof quality directly within your existing environment.

What is the best way to ensure consistency across multiple Lean 4 proof files?

The best way to ensure consistency is applying a comprehensive, structured checklist that provides a systematic approach to reviewing Lean proofs for thoroughness and quality standards.

When should I run a structured proof review on my Lean files?

Run a structured proof review when you need to maintain high-quality Lean proofs and want to ensure thoroughness, consistency, and mechanical cleanup across your codebase.