proof-repair

# Proof-Repair — Literature-Backed Repair Plans for Mathematical Proofs > 🔬 **Model Recommendation**: Run this skill on **Claude Opus** for best results. > Repair design + literature verification requires deep reasoning. If your session is > not on Opus, run `/model opus` before invoking. Heavy reasoning (literature search, > verification, full proof writing) will use Opus sub-agents. Takes a `/proofcheck` audit (or a raw .tex file with known issues) and produces self-consistent repair plans with new literature references for every fixable issue. **Pipeline position**: ``` /proofcheck → [THIS SKILL] → /proof-writer Find issues Fix + literature Write complete proofs ``` **Upstream**: `/proofcheck` (produces audit/ with provability triage + blockage reports) **This skill**: audit/ → REPAIR_PLAN.md + patched .bib + per-unit repair files **Downstream**: `/proof-writer` (writes complete corrected proofs for each repair) **Register for any proof text this skill writes.** Full-proof creation delegates to `/proof-writer`, which carries the register. But LaTeX patches this skill writes directly (Fill-Skipped-Steps, Insert-Lemma, inserted derivations) must follow the same Big Four register: key steps on display lines, connectives naming the logical move (displays carry the *what*, connectives the *why*), no walls of undisplayed algebra, no `Step 1 / Step 2` bulletization. Single source of truth: the "Mathematical Register and Readability (Big Four)" section of `../stat-sh...