roach overleaf

The repo is a clone of the Overleaf project. Collaborators type in the web
editor; their edits arrive as commits on main, the only branch Overleaf has.

git pull                                      # before touching any paper source
pixi run compile                              # after each logical change; it must pass
git commit -am "<what changed>" && git push

Do this unasked, after every major set of changes, not at the end of the session.
The build passes with undefined references, so after any label or notation
change, yours or a collaborator's, also check the log:

grep -n 'Reference.*undefined' build/main.log

• A refused push means someone typed since your pull: git pull, build again
  if .tex came in, push. Never force, never rebase. While someone is typing
  this happens on most pushes; repeat pull and push a few times before treating
  it as a problem.
• A conflict keeps both people's intent. A collaborator's prose is never
  dropped; where the edits disagree on content, theirs stays in the text,
  yours goes in a \todo{}, and the human is told.

Editing collaborators' text

The prose was written with care by other people. Make the smallest edit that
implements the request.

• Keep their sentences, terminology, headings and notation verbatim unless the
  request is to change them. Do not rephrase, restructure or tidy around the
  change.

• Before pushing, word-diff each touched section against its version before
  your edits. Every hunk should trace back to a request.

  git diff --word-diff <commit before your edits> -- Sections/Method.tex

• If a change forces edits elsewhere (renamed notation, a removed label, the
  appendix), keep those minimal too and list them in the reply.

@claude comments

Requests arrive inside the authors' comment macros, e.g.
\rishabh{@claude remove enumerate}. Any capitalization counts (@Claude).

Only when the human explicitly asks to watch for comments, start the watcher as
a Bash command with run_in_background, from the repo root. Never start it
unasked, and not merely because this skill loaded:

bash .claude/skills/roach-overleaf/scripts/claude-watch.sh      # [poll-seconds], default 30

It polls until there is something to say: it fetches, never touching the working
tree, and when @claude comments appear that it has not reported before
(including the ones already open when it first starts) it prints one NEW <file>:<line>: <comment> line each and exits. Its exit is what wakes you, and
its last line tells you to start it again. It remembers what it reported in
.git/claude-watch.seen, so a comment you left in place does not fire again.

When it exits, the first thing you do, before reading anything, is start it
again the same way (the human's request covers restarts until they say stop).
Only then: git pull, read each comment in full in the file
(the line is truncated and a comment may span lines), address it under the rules
above, build, commit, push, and report what changed, without waiting for the
human. If a comment is unclear, ask in the reply and leave the comment in place.

Address each one, then delete that comment and only that comment. Every other
author comment stays, including ones you believe are resolved, unless the human
says otherwise.