proof-checker

Verifies and fixes LaTeX mathematical proofs via cross-model adversarial review with audit reports.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/Lingjie-wang/autoRL --skill proof-checker-lingjie-wang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proof-checker
Source: https://github.com/Lingjie-wang/autoRL/tree/main/Auto-claude-code-research-in-sleep/skills/proof-checker
Command: npx skills add https://github.com/Lingjie-wang/autoRL --skill proof-checker-lingjie-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mathematical proofs in research papers often contain hidden gaps, unjustified steps, illegal limit interchanges, and unstated assumptions that are hard to catch by self-review. This Skill rigorously verifies LaTeX proofs using an external non-Claude reviewer model, fixes each identified gap with full derivations, and produces a formal audit report. ## Core Features & Use Cases - Cross-Model Adversarial Review: Submits proofs to an external reviewer backend (Codex or Manual Review MCP) at xhigh reasoning effort across up to 3 review rounds, threading reviewer memory so fixes are checked against the original gaps. - Structured Issue Taxonomy: Classifies findings across 20 categories in 4 groups (logic, analysis/measure theory, parameter tracking, scope) with a two-axis severity system (FATAL/CRITICAL/MAJOR/MINOR). - Proof-Obligation Ledger: Builds a dependency DAG, assumption ledger, typed symbol table, canonical quantified statements, and micro-claim inventory before review. - Fix & Re-Review Loop: Implements fixes directly in the .tex file (with optional --deep-fix repair-grade plans), runs counterexample red-teaming, blind re-review of FATAL/CRITICAL fixes, and optional --restatement-check for theorem statement drift. - Use Case: A researcher finishing a theory paper runs the checker on main.tex; it flags an unjustified dominated-convergence interchange in Lemma 3, derives the missing domination argument, patches the LaTeX, and emits PROOF_AUDIT.md plus a formal proof_audit_report.tex. ## Quick Start Ask the assistant to run the proof-checker skill on your paper's main.tex file to verify every theorem and lemma and generate an audit report.

Frequently Asked Questions about proof-checker

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

FAQPage Schema
How do I verify a mathematical proof in a LaTeX paper with AI?

Run the proof-checker skill on your main .tex file. It reads the full proof, builds a proof-obligation ledger, submits the content to an external reviewer model at xhigh reasoning effort, fixes identified gaps, and re-reviews until the acceptance gate passes.

What kinds of proof errors does automated proof review catch?

It catches 20 issue categories including unjustified assertions, quantifier errors, illegal limit/integral interchanges, missing domination for DCT, hidden assumptions, circular dependencies, non-uniform big-O claims, and scope overclaims, each rated FATAL through MINOR.

Why must the proof reviewer be a non-Claude model?

The executor is Claude, so routing review to any Claude product makes Claude judge its own work and voids the cross-model invariant. The default backend is Codex at xhigh reasoning; a manual-review backend is supported but must also use a non-Claude model.

Can the proof checker fix the errors it finds automatically?

Yes. Phase 2 implements each fix directly in the .tex file with full derivations, choosing a strategy per issue (add derivation, strengthen assumption, weaken claim, or add reference). The --deep-fix flag requests repair-grade patch plans from the reviewer.

What happens if a proof cannot be fixed after all review rounds?

After 3 review rounds without passing the acceptance gate, it emits an honest Proof Unrecoverable Report listing blocking FATAL/CRITICAL issues, ranked salvage options, reusable proof parts, and recommended next steps instead of declaring success.

What is the --restatement-check option for proof verification?

It runs a cross-location consistency pass comparing canonical theorem statements against restatements in abstracts, summaries, and tables, detecting drift like dropped quantifiers, changed big-O exponents, or lost conditional assumptions. It is opt-in and advisory only.