{"skill":{"slug":"latex-revision-tracker","displayName":"LaTeX Revision Tracker","summary":"Systematic workflow for tracking, managing, and revising large LaTeX academic papers with version control, content integration, and quality assurance.","description":"---\nname: latex-revision-tracker\ndescription: Systematic workflow for tracking, managing, and revising large LaTeX academic papers with version control, content integration, and quality assurance.\nversion: 1.0.0\nhomepage: https://github.com/Larry-of-cosmotim/latex-revision-tracker\nmetadata:\n  openclaw:\n    emoji: 📐\n---\n\n# LaTeX Revision Tracker Skill\n\n## Overview\n\nThis skill provides a comprehensive workflow for managing revisions to large LaTeX academic papers (10+ pages, multiple sections, complex bibliographies). It emphasizes systematic version control, careful content integration, and quality assurance throughout the revision process.\n\n## When to Use\n\nUse this skill when:\n- Revising large academic papers or dissertations in LaTeX\n- Integrating new content (figures, data, analysis) into existing manuscripts\n- Collaborating on multi-author academic documents\n- Preparing papers for journal submission with multiple revision rounds\n- Managing complex manuscripts with extensive bibliographies and cross-references\n\n## Core Workflow\n\n### 1. Version Control Setup\n\n**File Naming Convention:**\n```\nmanuscript_v1_initial.tex\nmanuscript_v2_reviewer_response.tex  \nmanuscript_v3_final_submission.tex\n```\n\n**Change Documentation:**\nCreate `version_changes.md` for each revision:\n```markdown\n# V2 TO V3 CHANGES SUMMARY\n\n## CHANGES MADE:\n### ✅ NEW SECTION ADDED:\n- **Section 4.2**: Glass Limit Analysis  \n- **Location**: After thermal conductivity discussion\n- **Content**: 3 paragraphs + 1 figure\n\n### ✅ NEW FIGURE:\n- **cahill_plot.pdf** - Publication-ready (300 DPI)\n- **Reference**: Figure~\\ref{fig:cahill_plot}\n- **Caption**: [Complete caption text]\n\n### ✅ CONTENT MODIFICATIONS:\n- Updated abstract (lines 25-35)\n- Revised conclusion (Section 6, paragraph 2)\n- Added 12 new citations\n\n## INTEGRATION DETAILS:\n- **Placement**: After existing analysis, before discussion\n- **Line numbers**: Approximately 450-480\n- **Compilation status**: ✅ Success / ❌ Unicode issues\n```\n\n### 2. Content Integration Strategy\n\n**Pre-Integration Checklist:**\n- [ ] New content reviewed for accuracy and style\n- [ ] Figures prepared in publication quality (PDF/EPS preferred)\n- [ ] All citations properly formatted and verified\n- [ ] Mathematical notation consistent with existing document\n- [ ] Cross-references planned (`\\label{}` and `\\ref{}` commands)\n\n**Integration Process:**\n```\n1. Backup current working version\n2. Identify integration point in document structure\n3. Plan figure/table placement and numbering\n4. Insert content with proper sectioning\n5. Update cross-references throughout document\n6. Compile and resolve errors iteratively\n```\n\n### 3. LaTeX-Specific Quality Control\n\n**Compilation Workflow:**\n```bash\n# For bibliography updates (full workflow)\npdflatex manuscript.tex\nbibtex manuscript\npdflatex manuscript.tex\npdflatex manuscript.tex\n\n# For minor changes (quick check)\npdflatex manuscript.tex\npdflatex manuscript.tex\n```\n\n**Common Issues and Solutions:**\n\n**Unicode Characters:**\n```latex\n% Problem: Special characters (κ, α, β) in text\n% Solution: Use math mode or proper packages\n\\usepackage[utf8]{inputenc}\n\\usepackage[T1]{fontenc}\n\n% In text: $\\kappa$ not κ\n% In equations: \\begin{equation} \\kappa = ... \\end{equation}\n```\n\n**Reference Resolution:**\n```latex\n% Ensure labels come after what they reference\n\\section{Results}\n\\label{sec:results}  % ✅ After section\n\n\\begin{figure}\n\\includegraphics{plot.pdf}\n\\caption{Important results}\n\\label{fig:results}  % ✅ After caption\n\\end{figure}\n```\n\n**Float Management:**\n```latex\n% For flexible placement\n\\begin{figure}[htbp]\n\n% To force exact position (use sparingly)\n\\usepackage{float}\n\\begin{figure}[H]\n\n% For wide figures in two-column format\n\\begin{figure*}[t]\n```\n\n### 4. Academic Content Integration\n\n**Section-Specific Integration Guidelines:**\n\n**Abstract Updates:**\n- Maintain 150-250 word limit\n- Update contribution statements to reflect new content\n- Ensure keywords remain accurate\n\n**Introduction Modifications:**\n- Integrate new motivation naturally\n- Update contribution list if needed\n- Maintain logical flow from general to specific\n\n**Related Work Additions:**\n- Group new citations thematically\n- Compare explicitly with existing approaches\n- Maintain chronological awareness\n\n**Results Section Integration:**\n- Number figures/tables consecutively\n- Reference all new content in text\n- Maintain consistent data presentation style\n\n**Discussion/Conclusion Updates:**\n- Integrate implications of new findings\n- Update limitations section if applicable\n- Revise future work based on new insights\n\n### 5. Bibliography Management\n\n**Citation Integration Process:**\n1. Add new entries to `.bib` file\n2. Use consistent citation keys (`author2024keyword`)\n3. Verify all required fields (author, title, year, venue)\n4. Check for duplicate entries\n5. Run `bibtex` to update references\n6. Resolve any citation warnings\n\n**Citation Style Consistency:**\n```latex\n% In-text citations\nRecent work has shown \\cite{smith2024analysis}...\nMultiple studies \\cite{jones2023,brown2024,wilson2024} have...\nAs demonstrated by Smith et al.~\\cite{smith2024analysis}...\n\n% Reference formatting (depends on journal style)\n% IEEE: [1] A. Smith, \"Title,\" Journal, vol. 1, pp. 1-10, 2024.\n% ACM: [1] Smith, A. 2024. Title. Journal 1, 1 (2024), 1-10.\n```\n\n### 6. Quality Assurance Process\n\n**Pre-Submission Checklist:**\n- [ ] Document compiles without errors or warnings\n- [ ] All figures appear correctly and are referenced in text\n- [ ] All tables are properly formatted and referenced\n- [ ] Bibliography is complete and properly formatted\n- [ ] Cross-references resolve correctly\n- [ ] Page layout is consistent with journal requirements\n- [ ] Mathematical notation is consistent throughout\n- [ ] Acronyms defined on first use\n- [ ] Line spacing and margins correct for submission\n\n**Collaboration Workflow:**\n```\n1. Author A makes changes → commits with detailed message\n2. Author B reviews changes → suggests modifications\n3. Changes documented in version log\n4. Final integration by designated \"manuscript manager\"\n5. All co-authors review final version before submission\n```\n\n### 7. Error Resolution Strategies\n\n**Common LaTeX Errors:**\n\n**Missing References:**\n```\nLaTeX Warning: Reference `fig:unknown' undefined\nSolution: Check \\label{} and \\ref{} spelling, compile twice\n```\n\n**Overfull/Underfull Boxes:**\n```\nOverfull \\hbox (15.0pt too wide)\nSolution: Rephrase text, add hyphenation hints (\\-), or use \\sloppy\n```\n\n**Float Issues:**\n```\nToo many unprocessed floats\nSolution: Add \\clearpage or adjust float placement options\n```\n\n**Bibliography Errors:**\n```\nCitation `unknown2024' undefined\nSolution: Check .bib file, run bibtex, compile again\n```\n\n### 8. Performance Optimization\n\n**For Large Documents (50+ pages):**\n- Use `\\includeonly{}` to compile specific chapters\n- Split large documents with `\\input{}` or `\\include{}`\n- Use `\\graphicspath{}` for organized figure directories\n- Consider `latexmk` for automated compilation management\n\n**Memory Management:**\n```latex\n% For documents with many figures\n\\usepackage{graphicx}\n\\DeclareGraphicsExtensions{.pdf,.eps,.png,.jpg}\n\n% For complex bibliographies\n\\usepackage[backend=bibtex,style=ieee]{biblatex}\n```\n\n## Advanced Features\n\n### 1. Diff Tracking\n\n**CRITICAL:** Diff files inherit ALL citation dependencies from the source documents. You MUST run the full bibliography workflow — a single `pdflatex` pass will ALWAYS produce citation errors (`[?]` markers) in diff files. This is the most common mistake.\n\n**Full diff workflow (mandatory — no shortcuts):**\n```bash\n# Step 1: Generate the diff .tex\nlatexdiff manuscript_v1.tex manuscript_v2.tex > diff_v1_v2.tex\n\n# Step 2: Copy bibliography files to the same directory\n# The diff file needs access to the SAME .bib files and .bst style\ncp manuscript.bib .    # if not already present\n\n# Step 3: Full compilation (ALL steps required)\npdflatex diff_v1_v2.tex      # First pass — generates .aux with citation keys\nbibtex diff_v1_v2            # Resolves citations from .bib file\npdflatex diff_v1_v2.tex      # Second pass — incorporates bibliography\npdflatex diff_v1_v2.tex      # Third pass — resolves all cross-references\n```\n\n**Never do this:**\n```bash\n# WRONG — will produce [?] for every citation\npdflatex diff_v1_v2.tex   # single pass = broken citations\n```\n\n**Troubleshooting citation errors in diff files:**\n- `[?]` markers → you skipped `bibtex`. Run the full 4-step workflow above.\n- `I couldn't open file name.bib` → copy the `.bib` file to the diff directory.\n- `I couldn't open style file name.bst` → copy the `.bst` file too.\n- Still broken → check that `\\bibliography{}` and `\\bibliographystyle{}` paths are correct in the source `.tex` files before running `latexdiff`.\n\n**Post-diff cleanup:** After the diff PDF is verified, remove all intermediate files. Only the final PDF should remain.\n```bash\n# Clean up all auxiliary and intermediate files\nrm -f diff_v1_v2.tex diff_v1_v2.aux diff_v1_v2.log diff_v1_v2.out \\\n      diff_v1_v2.bbl diff_v1_v2.blg diff_v1_v2.toc diff_v1_v2.lof \\\n      diff_v1_v2.lot diff_v1_v2.synctex.gz diff_v1_v2.fls \\\n      diff_v1_v2.fdb_latexmk diff_v1_v2.nav diff_v1_v2.snm\n# Keep only: diff_v1_v2.pdf\n```\n\n**Rule:** Always clean up after generating a diff PDF. The diff `.tex` file is a throwaway — it's auto-generated and can be recreated anytime from the two source versions. Never keep it around to clutter the workspace.\n\n### 2. Automated Quality Checks\n```bash\n# Check for common LaTeX issues\nlacheck manuscript.tex\n\n# Count words (approximate)\ntexcount manuscript.tex\n\n# Validate bibliography\nbibtex manuscript 2>&1 | grep -i warning\n```\n\n### 3. Collaborative Tools\n```bash\n# Git integration for version control\ngit add manuscript_v3.tex version_changes.md\ngit commit -m \"Add glass limit analysis section, update abstract\"\ngit tag v3.0-submission\n\n# Overleaf sync for real-time collaboration\ngit push overleaf master\n```\n\n## Templates\n\n### Change Log Template\n```markdown\n# VERSION X.Y CHANGES\n\n## SUMMARY\nBrief description of major changes\n\n## NEW CONTENT\n- Section/subsection additions\n- Figure/table additions  \n- New citations (count)\n\n## MODIFICATIONS\n- Sections revised\n- Figures updated\n- Text corrections\n\n## TECHNICAL NOTES\n- Compilation status\n- Package updates needed\n- Known issues\n\n## REVIEW STATUS\n- [ ] Content reviewed by Author A\n- [ ] Figures checked by Author B  \n- [ ] Bibliography verified\n- [ ] Final compilation successful\n```\n\n### Integration Checklist Template\n```markdown\n## PRE-INTEGRATION\n- [ ] Content accuracy verified\n- [ ] Style guide compliance checked\n- [ ] Citations properly formatted\n- [ ] Figures publication-ready\n\n## INTEGRATION\n- [ ] Placement planned\n- [ ] Cross-references updated\n- [ ] Numbering scheme maintained\n- [ ] LaTeX syntax verified\n\n## POST-INTEGRATION\n- [ ] Document compiles successfully\n- [ ] All references resolve\n- [ ] Visual layout acceptable\n- [ ] Change log updated\n```\n\n## Best Practices\n\n1. **Always backup** before major changes\n2. **Document everything** in change logs\n3. **Test compilation early** and often\n4. **Use consistent naming** for files and labels\n5. **Review systematically** with checklists\n6. **Collaborate deliberately** with clear ownership\n7. **Plan integration** before making changes\n8. **Maintain quality** throughout the process\n\n## Common Pitfalls\n\n- **Skipping documentation**: Change logs save time later\n- **Inconsistent compilation**: Always run full workflow for bibliography\n- **Poor float placement**: Plan figure integration carefully\n- **Missing backups**: One corrupted file can lose days of work\n- **Rushed integration**: Quality issues compound in large documents\n- **Ignoring warnings**: Small issues become large problems\n\n## Tools and Resources\n\n**Essential Tools:**\n- LaTeX distribution (TeX Live, MiKTeX)\n- PDF viewer with refresh capability (SumatraPDF, Skim)\n- Text editor with LaTeX support (TeXstudio, VS Code with LaTeX Workshop)\n- Reference manager (Mendeley, Zotero, BibTeX)\n\n**Quality Assurance:**\n- `latexdiff` for visual change tracking\n- `lacheck` for syntax validation\n- `texcount` for word counting\n- Git for version control\n\nThis skill provides the systematic approach needed to manage complex LaTeX academic papers while maintaining quality and avoiding common pitfalls that plague large document revision processes.","tags":{"latest":"1.0.0"},"stats":{"comments":0,"downloads":552,"installsAllTime":0,"installsCurrent":0,"stars":0,"versions":1},"createdAt":1773594043654,"updatedAt":1778491928981},"latestVersion":{"version":"1.0.0","createdAt":1773594043654,"changelog":"Initial release — revision workflows, version control, QA checklists, full bibliography workflow for diffs","license":"MIT-0"},"metadata":{"setup":[],"os":null,"systems":null},"owner":{"handle":"larry-of-cosmotim","userId":"s1776gcc9cdc3b5ecjqwrgtb3983nsv1","displayName":"Larry-of-cosmotim","image":"https://avatars.githubusercontent.com/u/264706805?v=4"},"moderation":null}