ai-asset-pricing: Skill for Claude Code

LaTeX Doctor Skill

The "clean room" skill. Run to get a .tex file into a consistent, compilable state with verified section markers.

Examples

• /latex-doctor -- full cleanup of the main .tex file
• /latex-doctor comments -- only strip comments
• /latex-doctor markers -- only verify section markers
• /latex-doctor compile -- only fix compilation issues
• /latex-doctor path/to/file.tex -- clean a specific file

Workflow

Step 1: Initial Compile

1. Run the compile command (use pdflatex/bibtex paths from canonical local state reported by tools/bootstrap.py audit, or a repo-root compatibility shim if present):

   cd {latex_dir} && pdflatex -interaction=nonstopmode {file} && bibtex {stem} && pdflatex -interaction=nonstopmode {file} && pdflatex -interaction=nonstopmode {file}
   

2. Parse the log for:
   • Errors: count and categorize (missing packages, undefined commands, etc.)
   • Warnings: overfull/underfull hbox, missing references, font warnings
3. Report: "Current state: N errors, M warnings"

Step 2: Comment Cleanup

Scan the .tex file and remove unnecessary comments:

REMOVE:

• Lines that are 100% LaTeX comments (% some old note)
• Trailing inline comments (keep the code, strip the % comment part)
• Blocks of commented-out code (% \begin{table}...% \end{table})

PRESERVE (never touch):

• %% BEGIN key and %% END key section markers
• % !TeX directives
• % inside \url{}, \verb||, or verbatim environments
• Comments that are clearly documentation (start with %% NOTE: or similar)

Report: "Removed N comment lines (K characters saved)"

Step 3: Verify Section Markers

Verify %% BEGIN/END markers for consistency.

1. Scan the .tex file for all %% BEGIN key and %% END key markers
2. If the project's CLAUDE.md defines registered section keys, cross-reference against them
3. Check for:
   • Missing markers: \section{} commands without %% BEGIN/END pairs
   • Orphaned markers: %% BEGIN key without matching %% END key (or vice versa)
   • Unknown keys: Markers with keys not in the registered list (if one exists)
   • Ordering: %% END key appears before the next %% BEGIN key
4. Fix any issues found, or flag for human review if ambiguous