proof-checker

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

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill proof-checker-nitrogen216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: proof-checker
Source: https://github.com/Nitrogen216/awesome-dsh-mods/tree/main/modes/dsh-autoresearch/vendor/aris-upstream/skills/proof-checker
Command: npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill proof-checker-nitrogen216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mathematical proofs in theory papers often contain hidden gaps, unjustified interchanges, and unstated assumptions that are hard to catch through self-review. This Skill systematically audits a LaTeX proof using an independent cross-model reviewer, fixes each identified gap with full derivations, and produces a formal audit report. ## Core Features & Use Cases - Cross-Model Adversarial Review: Submits the full proof to a non-Claude reviewer backend (Codex or Manual Review MCP) at ultra reasoning effort, checking hypothesis discharge, inequality chains, limit interchanges, quantifier order, and degenerate cases against a 20-category issue taxonomy. - Proof-Obligation Ledger: Builds a dependency DAG, assumption ledger, typed symbol table, canonical quantified statements, and micro-claim inventory in PROOF_SKELETON.md before judging validity. - Iterative Fix-and-Re-Review Loop: Applies severity-ordered fixes (FATAL to MINOR) directly in the .tex source, re-reviews up to 3 rounds, runs blind second reviews on critical fixes, and compiles with pdflatex to confirm no errors. - Use Case: A researcher finishing a theory paper runs the skill on main.tex; it flags an illegal dominated-convergence interchange in Lemma 4, derives the missing domination argument, patches the LaTeX, and emits PROOF_AUDIT.md plus a formal proof_audit_report.tex. ## Quick Start Ask the agent to verify the proof in your paper's main.tex file, optionally enabling --deep-fix for repair-grade fix plans or --restatement-check to detect theorem statement drift across sections.

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?▼

Point the skill at your main .tex file and it reads the full proof, builds a proof-obligation ledger, then submits the content to a cross-model reviewer at ultra reasoning effort. It classifies every issue by severity, fixes gaps with full derivations, and re-reviews until the acceptance gate passes.

What kinds of proof errors does automated proof checking detect?▼

It detects 20 issue categories across four groups: logic and structure gaps, illegal limit or expectation interchanges, missing domination or integrability conditions, hidden assumptions, quantifier errors, dimension tracking mistakes, and scope overclaims. Each issue gets a status and impact rating from FATAL to MINOR.

Why does proof review require a non-Claude reviewer model?▼

The executor is Claude, so routing the review to any Claude product would make Claude judge its own work and void the cross-model invariant. The reviewer must be an OpenAI, Google, DeepSeek, Moonshot, or Qwen model that the system can classify.

Can the proof checker fix the gaps it finds automatically?▼

Yes. Phase 2 derives each fix mathematically, edits the .tex file while preserving labels, and logs the change in PROOF_AUDIT.md. The optional --deep-fix flag requests repair-grade patch plans from the reviewer that the executor applies in one editing pass.

What are the limitations of automated proof verification?▼

The loop caps at three review rounds and relies on the reviewer model's mathematical capability, so it cannot guarantee correctness like a formal proof assistant such as Lean or Coq. Counterexample candidates are only marked confirmed when algebraically verified.