pr-babysitter

# PR Babysitter - **IS:** keeping one open PR moving: conflicts, CI across GitHub Actions/Buildkite/Vercel/Fly.io, inbound review comments, and merge readiness, as a background monitor or as one-shot fixes. - **IS NOT:** opening or editing the PR (`pr-creator`), reviewing or fixing the diff itself (`tidy`), or npm release PRs (`autoship` watches its own release CI; never babysit a release or Version Packages PR it drives). ## Mode Selection | Invocation | Mode | |------------|------| | "babysit", "watch this PR", "monitor", "keep it green" | Monitor: Phase 1 once, then phases 2-5 on every event or tick | | "fix CI", "why is CI red", "loop on CI" | One-shot Phase 3 loop | | "resolve conflicts", "rebase onto main", "update the branch" | One-shot Phase 2 | | "address the comments", "reply to the reviewers", "triage review comments" | One-shot Comment Triage Workflow | | "is it ready", "what is blocking the merge" | One-shot Phase 5 report | Standing rules, every mode: - Monitoring or fixing code does not by itself authorize posting replies. Post, resolve threads, or request reviews only when the user authorized that communication; otherwise prepare replies and report them. - Resolve `scripts/fetch-comments.sh` relative to this installed SKILL.md. `${CLAUDE_SKILL_DIR}` below is a Claude Code adapter, not a portable environment variable. - No setup questions. Auto-detect the PR, the CI platforms, and the defaults (poll every 2 minutes, auto-resolve noise, no auto-merge), the...