Skip to content

babysitter

Plate IV

Gallina patiens

Habitat
One pull request, a repository, or an organization, within the scope you state.
Diet
Review findings, red checks, and base-branch drift.
Field marks
"Review" alone authorizes inspection only. Pushes to the PR branch only. Never bypasses protected-branch rules. T3 owns the watch.

Carry pull requests through review and CI.

When to use it

A PR needs fixes and follow-up through review, CI or conflicts. Start with one named PR; repository and organization scopes can involve many branches and costs.

Try it

After installation, run in your terminal:

t3-plugins prompt babysitter doctor

Paste the printed line into a T3 thread attached to your project. Once readiness is clear, generate a task prompt:

t3-plugins prompt babysitter pr https://github.com/OWNER/REPO/pull/NUMBER 'Inspect reviews and CI only. Report blockers; do not edit, post, push or merge.'

Paste that output into T3. Replace the sample task or path with your own. If you installed skill adapters, select t3-babysitter from / and append the same request instead.

Operations

doctor, pr, repo, org. The entry file names the file to load for each operation.

What you get

Findings against the current PR head, check status and exact remaining blockers. When you authorize maintenance, the agent fixes eligible problems and observes the result. A green local test, armed auto-merge and an actual merge are different outcomes. T3 owns the watch and wakes the thread for later events.

Authorize the finish line

The example above requests inspection. To let it land the PR, state that scope:

t3-plugins prompt babysitter pr https://github.com/OWNER/REPO/pull/NUMBER 'Babysit through merge: fix review findings and CI, push to this PR branch, and merge once current-head requirements pass.'

Use repo OWNER/REPO or org OWNER only when you intend that wider scope. Protected branch rules remain required. Unknown or unsafe changes stay blocked.

Limits

T3 watches existing PRs. Discovering future PRs across a repository or organization requires a separately authorized scheduled sweep. See compatibility for the distinction between deterministic tests and live provider results.