proof-review-checklist

Automate Lean proof review with structured checklists and cleanup commands.

112|9|Updated Feb 17, 2026

Search Tags:#code review #formal verification #lean #proof quality #tactic optimization

Ready to run

npx skills add https://github.com/kim-em/lean-zip --skill proof-review-checklist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: proof-review-checklist
Source: https://github.com/kim-em/lean-zip/tree/main/.claude/skills/proof-review-checklist
Command: npx skills add https://github.com/kim-em/lean-zip --skill proof-review-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a systematic approach to reviewing and improving the quality of Lean proofs, ensuring code clarity, maintainability, and adherence to best practices.

Core Features & Use Cases

Automated Quality Checks: Guides users through mechanical cleanup steps for Lean proofs.
Metric Tracking: Records and analyzes proof complexity metrics before and after cleanup.
Use Case: When reviewing a colleague's Lean proof, use this Skill to systematically identify and fix issues like redundant simp calls, dead have bindings, and opportunities for proof compression.

Quick Start

Use the proof-review-checklist skill to review the Lean file 'MyProof.lean'.

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 proofs for redundant tactics and dead code?▼

You can review Lean proofs for redundant tactics and dead code by applying a structured checklist that automates mechanical cleanup steps, identifies dead `have` bindings, and flags unnecessary tactical applications for removal.

What is the best way to track proof complexity metrics before and after cleanup?▼

Tracking proof complexity metrics during cleanup involves recording and analyzing the proof's measurements before and after applying structural improvements, ensuring consistent code compression and maintainability.

Can I automate the removal of redundant simp calls in Lean?▼

Yes, you can automate the removal of redundant `simp` calls by executing targeted commands from a proof review checklist that systematically identifies and fixes unnecessary tactical applications in your Lean code.

Does formal verification in Lean require specific tactical patterns for code review?▼

Formal verification code review in Lean requires adherence to specific tactical patterns and metric analysis to ensure consistent code improvement and to address proof complexity during the cleanup process.

How do I systematically improve Lean proof quality and maintainability?▼

To systematically improve Lean proof quality, use a structured checklist to guide mechanical cleanup, eliminate proof complexity, and enforce adherence to established tactical patterns for better code clarity.