skills.rest
jmg2027
jmg2027COMMUNITY
Explore all skills by this author →
GitHub

lake-build-verify

Run lake build and analyze Lean project errors and proof completeness.

1|Updated Apr 9, 2026
Search Tags:#automation#development#verification#build#lean#ci
One-click install
npx skills add https://github.com/jmg2027/Dynamic-Resolution-Lattice-Theory- --skill lake-build-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lake-build-verify
Source: https://github.com/jmg2027/Dynamic-Resolution-Lattice-Theory-/tree/main/.claude/skills/lake-build-verify
Command: npx skills add https://github.com/jmg2027/Dynamic-Resolution-Lattice-Theory- --skill lake-build-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill detects build failures and warnings in Lean E213 projects, ensuring code integrity.

Core Features & Use Cases

  • Build Completion Check: Runs lake build to verify if the Lean code compiles successfully.
  • Error and Warning Analysis: Identifies build errors or warnings to assist in troubleshooting.
  • Zero Sorry Verification: Checks for the absence of sorry in Lean files to ensure proof completeness.
  • Use Case: Developers can automate build verification during CI/CD pipelines to prevent deployment of broken code.

Quick Start

Run the verification to confirm that the Lean project builds cleanly and contains no unresolved sorrys.

Frequently Asked Questions about lake-build-verify

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

FAQPage Schema
How do I automate Lean build verification and check for unresolved proofs?▼

Lean build verification executes `lake build` to compile code, analyzes output for errors or warnings, and scans files to ensure zero unresolved `sorry` statements remain in the project.

How can I integrate Lean proof completeness checks into my CI/CD pipeline?▼

Integrate Lean proof completeness checks into CI/CD pipelines by executing automated build verification steps that parse shell command outputs, detecting build failures and ensuring no `sorry` statements are deployed.

What is the best way to detect build failures and warnings in Lean E213 projects?▼

Detect build failures and warnings in Lean E213 projects by running automated verification scripts that execute build commands, parse shell output, and identify compilation errors or proof warnings for troubleshooting.

Does this Lean build verification tool require any external dependencies?▼

Lean build verification requires no external dependencies, operating through internal scripts that run shell commands and parse output to analyze build status and proof completeness across multiple Lean modules.

Why should I check for sorry statements in my Lean codebase during development?▼

Checking for `sorry` statements during Lean development ensures proof completeness by verifying that no unresolved or placeholder proofs exist, maintaining clean and reliable codebases across multiple modules.

Related Skills

Explore More Software Engineering Skills→
Arthur742RamosArthur742Ramos
1

lean-build

Build, test, and debug Lean 4 projects using Lake.

Community
Basic
mvillmowmvillmow
18

extract-test-failures

Parse test logs to extract and categorize failures by type.

Community
Basic
samChang72samChang72
1

code-review

Automates code reviews to detect bugs, style violations, and performance issues in submissions via static analysis tools.

Community
Intermediate
edgeandnodeedgeandnode

code-check

Validate and lint Rust and shell scripts with cargo check, clippy, and shellcheck.

Official
Intermediate