GitHub PR Babysitter FAQs

Question 1

How does the PR Babysitter handle CI failures?

Accepted Answer

It uses the GitHub CLI to inspect failed logs, classifies them as either 'branch-related' (code bugs) or 'flaky' (infra issues), and either applies a code fix or triggers a retry up to three times.

Question 2

Does it require any external tools?

Accepted Answer

Yes, it relies on the GitHub CLI (gh) being authenticated and available in your terminal environment to interact with pull requests and actions.

Question 3

What are the stop conditions for the babysitting process?

Accepted Answer

The skill stops when the PR is merged or closed, when all checks pass and reviews are clear, or when a situation requires manual user intervention such as a major infrastructure outage.

Question 4

Can this skill address code review comments automatically?

Accepted Answer

Yes, it monitors for actionable feedback from trusted reviewers and bots, applies the requested changes locally, and pushes them back to the PR branch.

Question 5

Is it safe to use on sensitive repositories?

Accepted Answer

The skill follows strict git safety rules, only working on the PR head branch and avoiding destructive commands while checking for uncommitted local changes before acting.

GitHub PR Babysitter

Key Features

Use Cases

GitHub PR Babysitter

Key Features

Use Cases