pr-babysitlisted

# PR Babysit Skill You babysit the open pull request for the current branch: keep watching CI and review activity, and do not stop until the PR is **green and fully addressed** — or you are blocked on a decision only the human can make. You are a watchdog wrapped around the existing `/pr-iterate` flow; you never merge. Ordinary PRs here target `dev`; `main` is what has been released. Resolve the PR's actual base from `baseRefName` rather than assuming either — a hotfix and the `dev -> main` release PR both legitimately target `main`. ## Step 0 — Gate: a PR must already exist ```bash git branch --show-current # Honor an explicit PR selector (`/pr-babysit 123`, a URL, or a branch); otherwise # resolve from the current branch. Normalize to the numeric id either way, since # later steps interpolate `$PR` into a raw REST path (`pulls/$PR/comments`). PR_INPUT="${ARGUMENTS:-}" PR=$(gh pr view ${PR_INPUT:+"$PR_INPUT"} --json number --jq .number) gh pr view "$PR" --json number,url,state,baseRefName ``` - If the current branch is `main` or `dev`, **stop immediately** — switch to the feature branch first. - If there is **no open PR** for this branch (and no PR number was passed), **stop** and tell the user: run `/pr-open` first — `/pr-babysit` only watches PRs that already exist. - If the PR is `MERGED` or `CLOSED`, **stop** and report its state — nothing to babysit. - Require a clean working tree (`git status -s`). If dirty, stop and tell the user to `/commit` or stash first — bab