ziwaa-se

Tex Proof Check Kit — Development skill for Claude Code

Development community

Check the proofs already written in a LaTeX paper by translating them faithfully into Lean 4, with a team of Claude Code agents.

How to install Tex Proof Check Kit

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ziwaa-se/tex-proof-check-kit and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Tex Proof Check Kit does

Check the proofs already written in a LaTeX paper by translating them faithfully into Lean 4, with a team of Claude Code agents.

Alternatives in Development

  • Done Check — PUA Done Check — 用于没跑测试别说完成、已完成但没证据、done without proof、需要验收/回归/交付质量检查的场景 19.5k ★
  • Lean Canvas — Generate Lean Canvas with problem, solution, UVP, and metrics 7.8k ★
  • Ars Citation Check — ARS academic-paper citation-check mode — citation error report 4.5k ★

README

TeX Proof-Check Kit

**Check the proofs already written in a LaTeX paper by translating them faithfully into Lean 4**, with a team of [Claude Code](https://code.claude.com/docs) agents that review each other's work. Every numbered result (theorem, proposition, lemma, corollary) gets one of four verdicts:

Verdict Meaning
Verified unconditionally The paper's own proof compiles in Lean, with no unproved input
Verified conditionally It compiles, but relies on results the paper cites or does not prove. These are explicit, named Lean hypotheses that a person should check
Issue recorded A confirmed problem, located in the paper and classified by whose fault it is: false statement (ERROR), a justification that fails, a missing hypothesis, an uncovered case, an ambiguous domain
Unfinished Stopped, with the reason recorded. Never counted as an error in the paper

**Scope of this version.** The kit **verifies proofs that are already written**. It checks the argument the authors wrote, step by step, and reports exactly where it holds and where it fails. It does **not** repair proofs, search for different proofs, or edit the paper. When it finds a problem, it records the evidence and the minimal change that would remove it; when the authors revise the paper, it re-checks the changed results. A mode that also proposes and verifies corrections is planned; see the [Roadmap](#roadmap).


Example

[`examples/full-workflow`](examples/full-workflow/) is a two-page note with three results, taken through the whole workflow: a first check, a corrected version of the paper, a condition checked by a person, and the final report. Real output of one run:

Result First check After the authors' revision and a person's check
Lemma 2.1: $ab \le \frac{a^2+b^2}{2}$ Verified unconditionally unchanged (not re-checked: the lemma did not change)
Proposition 2.2: a refinement of Nesbitt's inequa