DEDUPED Hot AI repos, turned into use cases Get 5 a day

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

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

  • Research
  • Intermediate
  • 45 minutes
  • From the README
  • Any agent

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

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

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

What you need first

  • Python 3 installed to run pairtex.py (standard library only)
  • A local LaTeX project in a Git repository
  • A rendered HTML file of the manuscript, produced by the default make4ht renderer or an adapter
  • A coding agent of your choice to consume the feedback files

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 for your agent

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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page