proof-review-aggregate

Aggregates four specialized proof reviews into a final controller-facing proof_review.md with score and routing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple specialized reviewers (structural, rigor, citation, adversarial) independently evaluate a machine-learning theory proof, their findings must be reconciled into a single authoritative accept/reject decision with a clear repair route. This Skill performs that final aggregation, validating each specialized review against machine-readable contracts and emitting one controller-facing verdict. ## Core Features & Use Cases - Contract Validation: Verifies that all four specialized review artifacts use exact raw-token verdicts (PASS/BLOCKING), aligned repair depths, and valid repair targets before aggregation. - Aggregate Contract Gates: Runs independent checks on the LaTeX bundle, including compile/support, theorem self-containedness, assumption provenance, explicit-rate declarations, appendix full-derivation coverage, citation integrity, and template-instantiation hygiene. - Failure-Localized Routing: Selects the deepest blocking issue (idea > sketch > step > assembly) and maps it to a Failure Type, Suggested Next Action, and Retry Mode for the controller. - Use Case: After four specialized reviewers finish evaluating a theorem candidate's LaTeX proof bundle, run this Skill to produce the single proof_review.md that decides acceptance or routes the smallest repair. ## Quick Start Aggregate the completed structural, rigor, citation, and adversarial reviews for perspective_M/idea_N into the final proof_review.md with score, failure type, and retry routing.

Frequently Asked Questions about proof-review-aggregate

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

FAQPage Schema
How do I combine multiple proof review reports into one final decision?

Run this aggregator after all four specialized reviewers (structural, rigor, citation, adversarial) complete and pass contract gates. It validates each artifact, normalizes findings, selects the deepest blocker, and writes a single proof_review.md with score, failure type, and retry mode.

What happens if one specialized proof review is invalid or missing?

The aggregator stops and asks the controller to rerun or hand off only that specialized reviewer. It never writes proof_review.md from invalid diagnostic inputs, and invalid artifacts are treated as process failures rather than proof failure types.

Can a proof be accepted when all specialized reviewers pass?

Not automatically. The aggregator independently runs contract gates on the LaTeX bundle, including compile checks, theorem self-containedness, assumption provenance, explicit-rate declarations, and full appendix derivation coverage. Any aggregate blocker prevents acceptance even with four PASS verdicts.

How does the aggregator decide where to route a failed proof for repair?

It selects the deepest repair depth using the order idea > sketch > step > assembly, then maps it to a failure type and next action such as /proof-assembly, /proof-step <Step ID>, /proof-sketch, or /subagent-idea-generator. Ties resolve to the smallest local repair target.

What are the limitations of the aggregate proof review?

It does not redo the specialized reviews or modify proofs, sketches, or step artifacts. It only performs contract checks, consistency verification, issue normalization, scoring, and routing, relying on the specialized reviewers for substantive mathematical evaluation.