ce-babysit-pr
Babysit a PR
Keep an open PR continuously moving toward merge by reacting to three independent event streams — incoming review comments, CI status changes, and branch currency — as each arrives, for as long as the PR stays open. Comment fixes are delegated to ce-resolve-pr-feedback; CI failures are delegated to ce-debug; routine target-local base movement follows the bounded protocol below. This skill owns the watch loop: snapshot, order, dedup, act, and decide when to keep watching, move to the next authorized managed-stack layer, or stop.
Outcome: leave the requested PR at an honest terminal, looks-ready, blocked, or budget state under the run's posture (target | stack-ready | stack-land). For an independent PR or manual dependency chain, the target-local result is done. For a confirmed managed stack, a settled layer is a transition checkpoint governed by posture (below). Never infer stack-wide semantic scope from branch topology alone. Settled ≠ merged: a layer can look merge-ready while still OPEN; you do not need to merge to babysit the next layer.
Posture (one value for the invocation/run)
Hold exactly one posture for the run. Carrier: posture:target|stack-ready|stack-land — distinct from watch / checkpoint / mode:pipeline / duration. Re-state the same posture on every managed-stack layer --continue-invocation transition alongside the existing budget flags.
| Posture | Behavior |
|---|---|
target |
Only the named PR. Stop at looks-ready. May offer stack-wide once when a confirmed multi-layer managed stack needs work; decline keeps the target-local stop. Never merges. |
stack-ready |
After the active layer settles, automatically continue to the next open non-draft upstack layer that needs work. Never merges. Persist for the run; do not re-ask each layer. |
stack-land |
Like stack-ready for traversal. Selecting or handing off posture:stack-land is run-level land authorization. After settle, merge the bottom-most open settled PR via gh stack merge + gh stack sync, then continue. |
Selection: named one PR / no stack language → default target, but if confirmed multi-layer managed stack ask once (only this PR vs whole stack to ready). Intent to own/finish the stack → stack-ready. Intent to land/merge when green → stack-land. Prefer intent over keyword regex. An explicit "babysit the managed stack" request selects stack-ready (or stack-land when land intent is also clear). In mode:pipeline, use only the posture/scope already supplied on the invocation — never ask.
When a confirmed managed stack is in play and you need CLI recipes, load references/stack-commands.md.