# AI use cases for PairTeX (yuema137/PairTeX)

Repo: [yuema137/PairTeX](https://github.com/yuema137/PairTeX) | Use cases: 5 | Page: https://dedupedai.com/use-cases/yuema137-pairtex/

A local, Git-native review and feedback layer that renders an existing LaTeX repository to HTML so humans can comment and edit in place while a coding agent reads the recorded feedback.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Review a LaTeX paper in an HTML view and record feedback: https://dedupedai.com/use-cases/yuema137-pairtex/review-paper-in-html-with-agent/
- Have an agent apply reviewer feedback to the TeX source: https://dedupedai.com/use-cases/yuema137-pairtex/apply-review-feedback-to-tex-source/
- Try PairTeX on the bundled demo fixture: https://dedupedai.com/use-cases/yuema137-pairtex/try-pairtex-on-demo-fixture/
- Check a paper in ICLR, NeurIPS, or ICML wrappers: https://dedupedai.com/use-cases/yuema137-pairtex/check-paper-in-conference-template/
- Run the PairTeX test suite before tagging a release: https://dedupedai.com/use-cases/yuema137-pairtex/run-pairtex-test-suite-before-release/

## How to review a LaTeX paper in an HTML view and record feedback with PairTeX

Repo: [yuema137/PairTeX](https://github.com/yuema137/PairTeX) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Render your paper to HTML, comment and edit in the browser, and keep every action as a feedback file.

**Who it is for:** A paper author with a local LaTeX repo who wants a comfortable reading surface and wants feedback kept out of chat windows.

**The problem:** Reviewing with a coding agent usually means compiling a PDF and copying quotes and comments back into a chat by hand, so the manuscript and the feedback never sit in the same place.

**The outcome:** Comments, Edit-mode changes, and Review-mode proposals are saved as independent files under .pairtex/feedback/ while the original TeX stays untouched.

### Steps

1. Ask your coding agent to render the repo with the PairTeX skill, or run `python3 pairtex.py --project /path/to/paper --html /tmp/pairtex-rendered/main.html --port 8765` after rendering the HTML yourself. (inferred, check the README)
2. Open the URL printed by PairTeX in your browser.
3. Add comments, Edit-mode changes, or Review-mode proposals in the HTML page.
4. Check that the entries appear under /path/to/paper/.pairtex/feedback/.

### Prompt to paste into your agent

```text
Read and follow skills/pairtex-agent/SKILL.md in the PairTeX repo. Render the LaTeX repository at <paper-path> into a disposable HTML projection and start the local PairTeX view. Report the URL, source HEAD commit, dirty state, render command, and HTML output path, and confirm that no canonical source file changed.
```

### Caveat

The HTML view is a disposable projection that you must re-render after each TeX change, and PairTeX does not synchronize projections between users.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/yuema137-pairtex/review-paper-in-html-with-agent/

## How to have an agent apply reviewer feedback to the TeX source with PairTeX

Repo: [yuema137/PairTeX](https://github.com/yuema137/PairTeX) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Send feedback files to a coding agent that edits canonical TeX, rebuilds, and reports decisions.

**Who it is for:** A paper author who has finished reviewing in the HTML view and wants the agent to act on each entry.

**The problem:** Turning a list of comments into correct source edits is slow, and it is easy to lose track of which items were addressed.

**The outcome:** The agent changes only canonical source, rebuilds the paper, regenerates the HTML, resolves only the addressed items, and leaves the rest open with thread replies.

### Steps

1. Confirm the open entries exist in /path/to/paper/.pairtex/feedback/.
2. Send the consume-feedback prompt to your coding agent.
3. Wait for the agent to report the source diff, build result, render path, and feedback decisions.
4. Click `Refresh` in the PairTeX page to reload the latest HTML and feedback files.

### Prompt to paste into your agent

```text
Read and follow skills/pairtex-agent/SKILL.md in the PairTeX repo. Consume the open feedback in <paper-path>/.pairtex/feedback/, apply changes only to canonical TeX source, rebuild, and regenerate the HTML projection. Report the source diff, build result, and which entries were resolved, and verify that any unresolved entry has a thread reply.
```

### Caveat

The agent is expected to resolve only feedback it has actually addressed, so a human still has to check the source diff and the feedback decisions before committing.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/yuema137-pairtex/apply-review-feedback-to-tex-source/

## How to try PairTeX on the bundled demo fixture with PairTeX

Repo: [yuema137/PairTeX](https://github.com/yuema137/PairTeX) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Run the isolated demo to see comments, Edit and Review modes, and section navigation.

**Who it is for:** A developer or author who wants to see how PairTeX behaves before pointing it at a real paper.

**The problem:** It is hard to judge the review workflow from a description alone, and a real manuscript is a risky first test.

**The outcome:** You have a running local view of the fixture, with comments, formula editing, and section navigation working on synthetic content.

### Steps

1. Clone the PairTeX repository and change into its folder.
2. Run `python3 pairtex.py --project demo/fixture --html demo/fixture/rendered.html --port 8765`. (inferred, check the README)
3. Open the URL printed by PairTeX.
4. Add a comment, switch between Edit and Review modes, and check that feedback files appear under demo/fixture/.pairtex/feedback/.

### Prompt to paste into your agent

```text
Clone the PairTeX repository and run `python3 pairtex.py --project demo/fixture --html demo/fixture/rendered.html --port 8765` from its root. Report the URL that PairTeX prints and list the files created under demo/fixture/.pairtex/feedback/, then confirm that demo/fixture/main.tex was not modified.
```

### Caveat

The fixture uses synthetic content and does not show how PairTeX handles the private SIDERIUS paper or your own build workflow.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/yuema137-pairtex/try-pairtex-on-demo-fixture/

## How to check a paper in ICLR, NeurIPS, or ICML wrappers with PairTeX

Repo: [yuema137/PairTeX](https://github.com/yuema137/PairTeX) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README

Render the public conference-template demos to test formulas, citations, figures, and tables.

**Who it is for:** A researcher preparing a submission in one of the named conference styles who wants to confirm the HTML view handles that template.

**The problem:** Conference templates use different styles and macros, and it is unclear whether a review layer will render them correctly before you rely on it.

**The outcome:** You have rendered HTML for the chosen conference demo and a running local view showing formulas, citations, figures, tables, and sections.

### Steps

1. Install latexmk so the build command in the README can run.
2. Run `python3 pairtex_render.py --project demo/iclr --input main.tex --output /tmp/pairtex-iclr-rendered --build-command 'latexmk -pdf -interaction=nonstopmode -halt-on-error {input}'`. (inferred, check the README)
3. Run `python3 pairtex.py --project demo/iclr --html /tmp/pairtex-iclr-rendered/main.html --port 8766`. (inferred, check the README)
4. Open the printed URL and check formulas, citations, figures, and tables. (inferred) Repeat with demo/neurips/ or demo/icml/ by changing the project and output paths.

### Prompt to paste into your agent

```text
Read the PairTeX README in this repo and render the demo/iclr project with pairtex_render.py using the build command shown there. Report the render output path and the URL from pairtex.py, and list which of formulas, citations, figures, and tables rendered without errors.
```

### Caveat

The default renderer is make4ht and the build step depends on a working latexmk install, so a missing TeX toolchain will stop the render before PairTeX starts.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/yuema137-pairtex/check-paper-in-conference-template/

## How to run the PairTeX test suite before tagging a release with PairTeX

Repo: [yuema137/PairTeX](https://github.com/yuema137/PairTeX) | Difficulty: Advanced | Time: 15 minutes | Basis: From the README

Sync the dev environment with uv and run the unit tests, including the version check.

**Who it is for:** A maintainer or contributor who is about to change PairTeX code or prepare a tagged release.

**The problem:** A release tag should not have to move, so the code and version must be checked before tagging.

**The outcome:** The test suite passes in the pinned environment, and the version check confirms the declared release version matches the code.

### Steps

1. Install uv on your machine.
2. Run `uv sync` in the PairTeX repository root.
3. Run `uv run python -m unittest discover -s tests -t .`.
4. Work through docs/release-checklist.md before tagging.

### Prompt to paste into your agent

```text
Read the PairTeX README and docs/release-checklist.md in this repo. Run `uv sync` and then `uv run python -m unittest discover -s tests -t .`, and report the pass or fail count. Verify that tests/test_version.py passes so the version in pyproject.toml matches __version__ in pairtex.py.
```

### Caveat

The README pins the development environment to the minimum supported Python version, so a newer local interpreter alone will not show whether the code works on the oldest supported one.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/yuema137-pairtex/run-pairtex-test-suite-before-release/