babysitlisted

# Drive a PR to green — goal loop **GOAL:** PR **#$1** reaches `reviewDecision == APPROVED` — a *fresh* approval on the current head commit — with **all CI checks green** and `mergeable == MERGEABLE`. Loop until then. **A human still does the merge; you never merge.** Repo: the 2nd argument if given, otherwise the current repo (`gh repo view --json nameWithOwner --jq .nameWithOwner`). **To make it loop until the goal, run me under the loop skill:** `/loop /babysit $1` (self-paced — each pass does one check-react cycle, then either declares the goal met and ENDS the loop, or continues. You can also run me once for a single review-react pass.) ## Operating principles (non-negotiable) - **Verify every finding against the code — do not capitulate.** Open the file, run the check, read the diff. A reviewer (QA bot or human) can be wrong. Fix what's real; push back with evidence on what isn't. - **Always answer every review comment** with what you did — the fix + commit SHA, or the evidence-based reason you didn't change anything. Never leave one unanswered. - **Never merge.** Drive to approval only. - **Never mutate external state to turn a gate green.** If a check is red because of live server/environment state you didn't create (a deploy gate, a drift check, someone else's running job), you may diagnose read-only (SSH, logs, dashboards) but NOT delete/modify resources — they may be someone else's live workload. Report the cause and owner, notify the user, and keep looping at