kbabysit

Drives a GitHub PR through Copilot review rounds until merge-ready with scoped triage.

2|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/kpiteira/devops-ai --skill kbabysit-kpiteira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kbabysit
Source: https://github.com/kpiteira/devops-ai/tree/main/skills/kbabysit
Command: npx skills add https://github.com/kpiteira/devops-ai --skill kbabysit-kpiteira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request review loops with automated reviewers like GitHub Copilot can run indefinitely, burning paid review rounds on findings outside the PR's actual scope. This Skill bounds that loop: it requests reviews, triages findings against a written review scope, applies fixes, and stops when the reviewer has finished with the PR rather than with the fixes. ## Core Features & Use Cases - Bounded review loop: Requests Copilot reviews, waits for completion, triages each round via kreview, and stops on explicit signals (second-order findings, no in-scope items, round budget) instead of looping forever. - Scope-anchored triage: Every finding is judged against the PR body's ## Review scope section, with dispositions of IMPLEMENT, PUSH BACK, DISCUSS, or OUT OF SCOPE, and out-of-scope items filed as issues. - Auditable reporting: Posts a Babysit report comment on the PR with per-round provenance columns, effort levels, push-back reasoning, and a merge-ready or needs-decision verdict. - Use Case: After opening a milestone PR, run /kbabysit 42 from the PR's worktree; the loop requests Copilot review, addresses real findings, pushes fixes, and stops after the round where all findings sit on prior fix commits, ending with a TL;DR report for the human. ## Quick Start Run /kbabysit followed by the PR number from a session checked out on that PR's branch to drive it to merge-ready.

Frequently Asked Questions about kbabysit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I babysit a GitHub PR through Copilot review rounds?

Run /kbabysit with the PR number from a session checked out on the PR's branch. The loop requests the Copilot review, waits for it, triages findings via kreview, pushes fixes, and repeats until a stop condition fires, then posts a report.

How do I stop Copilot code review from looping forever on a PR?

Use scope-bounded stop rules: end the loop when all line-anchored findings sit on previous fix commits (second-order round), when no in-scope implementable items remain, or when a round budget is reached. Unreviewed fix commits get a kselfreview pass instead of another paid round.

Can I change the Copilot review effort level when requesting a review?

No. The review effort level (Lite or Balanced) is a repository or organization setting under Copilot code review settings, not a request-time parameter. The REST and GraphQL review-request APIs accept only reviewers, so the loop records the level per round but never changes it.

Why does kbabysit require a Review scope section in the PR body?

The Review scope section lists the outcomes the PR delivers, and every review finding is judged against it. Without it, anything in the diff is in scope by construction and the loop cannot distinguish real findings from out-of-scope noise.

What happens when the babysit round budget is reached?

The loop stops and reports a needs-human-decision verdict, since non-convergence within the budget means the disagreement is real. The default budget is 3 rounds, raised with the max-rounds argument, and all scope and provenance rules still apply.