Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Browser & automation

babysit

Drive a PR to a clean review (Greptile 5/5, zero open threads) — ships if needed, keeps it mergeable against staging, re-triggers both Greptile and cubic, fixes real findings, replies to and resolves every thread, and loops until clean

simstudioai · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add simstudioai/sim --skill babysit

About this skill


name: babysit description: Drive a PR to a clean review (Greptile 5/5, zero open threads) — ships if needed, keeps it mergeable against staging, re-triggers both Greptile and cubic, fixes real findings, replies to and resolves every thread, and loops until clean

Babysit PRs

Owns a PR end-to-end through review: ship it, wait for the automatic review round, and if it isn't already clean, drive fix → reply → resolve → re-review cycles until Greptile reports 5/5 and there are zero open comment threads, keeping the branch mergeable against staging along the way. Two bots review this repo — Greptile and cubic — and they behave differently; see "Two reviewers" below. Designed to be run under /loop (no fixed interval — let it self-pace on review latency) so it survives across multiple wakeups in the same session.

When to use

  • The user says "babysit this PR", "keep working the reviews until it's clean", or similar
  • As the natural follow-up to /ship when the user wants the review loop automated rather than manually re-triggering reviews and answering comments themselves

Inputs

Needs a PR number. If none is given and there's no open PR for the current branch, run /ship first (which includes the origin/staging sync check — see .agents/skills/ship/SKILL.md) to create one.

Two reviewers

Both post inline threads that count toward "clean", and they need re-triggering separately:

Greptile (greptile-apps)cubic (cubic-dev-ai)
VerdictConfidence Score: X/5 in a summary commentno score — only inline threads
Summary commentedited in place across roundsfresh review per run
Re-trigger@greptile@cubic-dev-ai review this PR
Latency1–3 min1–3 min

Post both after every push, as two separate comments. Triggering only Greptile is the easy mistake: the PR then shows 5/5 with cubic's threads still open from an earlier commit, and its findings never get re-checked against the fix.

@cubic-dev-ai review this PR is the documented wording — @cubic alone does not trigger it.

cubic reviews the commit that was HEAD when its run started, so a thread can describe code the next commit already changed. Before treating a cubic finding as real, check whether the current HEAD still has the problem — a stale round is a reply-and-resolve, not a fix.

Definition of "clean"

All three must hold:

  1. The latest Greptile summary comment reports Confidence Score: 5/5
  2. reviewThreads (GraphQL, see below) has zero threads with isResolved: false, from either bot
  3. Every check has finished and passed — gh pr checks <n> shows no fail and no pending. A red run is not clean no matter what the reviewers say, and the lint/audit jobs routinely catch what a local run misses. A pending one is not clean either: it has not reported yet, and treating "not failing" as "passing" reports the PR clean before CI has had its say. Wait for it — the step-10 stop condition covers a check that never settles.

Do not stop early on "no new comments this round" alone — a thread can be open from an earlier round, and cubic often lands its first threads a round after Greptile's. Always check all three conditions freshly after every push.

Loop

  1. Check current state before doing anything, including whether the PR is still mergeable:

    gh pr view <n> --json mergeable
    gh pr checks <n> | grep -v skipping
    gh pr view <n> --json comments -q '[.comments[] | select(.author.login=="greptile-apps")] | last | .body'
    gh api graphql -f query='
    query { repository(owner: "<owner>", name: "<repo>") { pullRequest(number: <n>) {
      reviewThreads(first: 50) { pageInfo { hasNextPage endCursor } nodes { id isResolved path line
        comments(first: 5) { nodes { id databaseId author { login } body } } } } } } }'
    

    The score is a line inside the body of Greptile's latest comment (| last | .body), which it edits in place across rounds. reviewThreads(first: 50) is a single page — check pageInfo.hasNextPage. If true, don't stop yet: re-run the same query with after: "<endCursor>" and keep paging until hasNextPage is false before evaluating "clean." A PR with more than 50 threads is rare but stopping on a partial page would silently miss unresolved ones past the cutoff. The query returns both bots' threads. A ReviewThread has no author of its own — identity lives on its comments, so read the opener's at comments.nodes[0].author.login and do not add an author field at the thread level, which makes the query fail to compile. If mergeable is CONFLICTING, fix that first (step 2). If a check is failing, fix that too — treat it exactly like a review finding. If a check is still pending, do not evaluate "clean" at all: go to step 9 and wait for it. Otherwise, if Greptile is 5/5, every thread across all pages has isResolved: true, and every check has finished and passed, stop — report the outcome (see "Reporting" below) and skip the rest of this list.

  2. If the PR has a merge conflict, merge origin/staging, resolve the conflicts, run the usual pre-push checks, push, and go to step 8 to re-trigger review.

  3. If no review has run yet (fresh PR, no bot comments): both run automatically on PR open — confirm via gh pr checks <n> (look for Greptile Review and cubic · AI code reviewer) and wait for both before doing anything else. They finish at different times, so a PR that looks clean because only one has reported is not clean yet.

  4. If a review round has landed and it isn't clean: for every thread where isResolved: false, triage the finding on its own merits — this is the part that requires judgment, not a mechanical loop:

    • Real bug: fix it in the cleanest way available. Match the codebase's existing conventions for that kind of problem before inventing a new one (e.g. an SSRF
Read the complete source ↗