melech-babysit

# Babysit PR ## What The User Is Trying To Achieve The user opened a PR and wants it merged without hand-holding every 30 seconds. Between iterations the world moves: teammates comment, the base branch advances, CI reruns, review bots (Bugbot, CodeRabbit, and friends) post new findings. A one-shot check goes stale within minutes. Your job is to keep the PR in "merge-ready" state on a recurring cadence until it merges, the user stops you, or something genuinely needs them. ## Loop Or You're Useless Default cadence: **every 5 minutes**. Accept overrides like `melech-babysit every 10m` or `melech-babysit 2m`. Arm the loop before doing anything else: - If the user has a `/loop` primitive in their setup, invoke it: `/loop 5m melech-babysit <PR ref>`. - Otherwise arm a background heartbeat with a unique sentinel and monitored output, then run one immediate iteration. One iteration doesn't count as babysitting. If you can't loop, say so and stop — don't pretend a single pass is enough. ## Per Iteration Do these in order. Skip a step only if the previous one produced a hard blocker. 1. **Refresh state.** `git fetch`, pull the PR branch, check whether base has advanced. Never trust cached PR data older than the last tick. 2. **Merge conflicts.** Resolve them intelligently, preserving intent on both sides. If intents genuinely conflict, abort the merge and surface the specific hunks to the user — do not guess. 3. **Comments.** Fetch only unresolved review thread...