proof-review-rigor

Audits assembled mathematical proofs for derivational rigor, quantifiers, constants, and boundary cases.

65|2|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/DechenZhang/VALG-ML-Theory-Agent --skill proof-review-rigor-dechenzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proof-review-rigor
Source: https://github.com/DechenZhang/VALG-ML-Theory-Agent/tree/main/skills/proof-review-rigor
Command: npx skills add https://github.com/DechenZhang/VALG-ML-Theory-Agent --skill proof-review-rigor-dechenzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Final mathematical proofs assembled from many proof steps can hide derivation gaps, drifted theorem statements, unproved assumptions, or compressed appendix arguments that undermine rigor. This Skill provides a diagnostic final review that checks every derivation line-by-line before a theorem candidate is accepted. ## Core Features & Use Cases - Derivation Auditing: Verifies theorem-level, assembly-level, and step-level derivations against accepted step artifacts, settings, and the LaTeX paper bundle. - Quantifier and Rate Discipline: Checks quantifier order, constants, parameter dependence, probability and convergence modes, explicit-rate declarations, and boundary or degenerate cases. - Repair Localization: Emits machine-readable diagnostic fields including verdict, blocking issues, suggested repair depth (assembly, step, sketch, or idea), and the smallest candidate repair target. - Use Case: After assembling a LaTeX proof manuscript from accepted proof steps, run this reviewer to confirm the appendix preserves all source derivations and the main theorem is self-contained before acceptance. ## Quick Start Run the rigor review on the assembled proof in perspective_M/idea_N after proof assembly to produce proof_review_rigor.md with a PASS or BLOCKING verdict.

Frequently Asked Questions about proof-review-rigor

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

FAQPage Schema
How do I review a mathematical proof for rigor before acceptance?

Run this reviewer after proof assembly. It maps every nontrivial derivation, checks line-by-line logical sufficiency against accepted step claims and dependencies, and writes proof_review_rigor.md with a PASS or BLOCKING verdict plus localized repair targets.

What does the rigor reviewer check in a LaTeX proof bundle?

It verifies theorem statements are self-contained with numbered assumption environments, notation is definitional only, internal references use theorem-style label/ref pairs, and the appendix preserves full derivations from accepted proof steps rather than compressed summaries.

When should I run proof-review-rigor in the workflow?

Run it after the proof assembly stage, once the LaTeX bundle, assembly report, accepted proof sketch, and all required accepted step proofs and reviews exist. It is a diagnostic reviewer and does not modify any proof artifacts.

What causes a BLOCKING verdict in proof rigor review?

Blocking issues include derivation gaps, hidden unproved assumptions, quantifier or probability-mode errors, missing explicit-rate bridges, compressed appendix proofs that drop source derivations, and theorem statements that drift from the accepted target.

Can the rigor reviewer fix or rewrite the proof it reviews?

No. It is strictly diagnostic: it emits verdict, blocking issues, suggested repair depth, and the smallest repair target, but never modifies proofs, sketches, step artifacts, or accepted results. Repairs route back to the responsible workflow stage.