Babysit PR

Many repos have AI review bots. They're helpful, even if they are not always right.

Waiting

Never write your own watcher, polling loop, or sleep loop. Use one watcher per PR: watch_pull_request in T3 Code, pr-wait everywhere else. Never run both on the same PR. Every watcher on a GitHub account shares one rate limit.

In T3 Code: watch_pull_request

Handle the existing checks and comments first. Then call watch_pull_request and end your turn. T3 Code wakes you with a message when a check fails, the required checks pass, someone comments or reviews, or the branch conflicts.

• Only the thread that owns the PR watches it. If you are a delegated child task (a reviewer, a Sol round, any delegate_task child), never call watch_pull_request. The parent owns the PR. Do not watch PRs you are not working on.
• A wake is news, not a merge decision. Check the merge gate yourself.
• Unwatch when you hand off. A watched thread stays in Working and out of the user's inbox. When you stop (ready, blocked, or asking the user a question), call unwatch_pull_request first. A merge or close ends the watch on its own.
• "Stopped watching, could not read it" usually means GitHub's rate limit is used up. Run gh api rate_limit --jq .resources.graphql before you watch again. If remaining is near 0, wait for reset with one background command, then watch again. Never watch again in a tight loop.

Everywhere else: pr-wait

Wait with scripts/pr-wait from this skill's directory (use its absolute path).

pr-wait <pr> [--repo owner/name] [--until ready|green|any-change]

It prints one line per real event. It exits 0 when the --until condition is met or the PR merges, 1 when it needs you (a required check failed, conflicts, unresolved threads, PR closed), and 2 on bad input.