Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
.claude/skills/thedotmack-babysit/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-20 | ✗→✓ | ▲ Improved | 5% | 0% |
| case-06 | ✓→✗ | ▼ Worse | 53% | 0% |
| case-16 | ✓→✗ | ▼ Worse | -19% | 0% |
| case-07 | ✓→✓ | = Same ✓ | 9% | 0% |
| case-08 | ✓→✓ | = Same ✓ | 12% | 0% |
Stay with the PR until it is actually clean. Do not stop after one check pass if comments or review threads are still unresolved.
Use gh pr view for the coarse status:
bashgh pr view <number> --json \ number,state,isDraft,mergeable,mergeStateStatus,reviewDecision,headRefOid,statusCheckRollup,url
Resolve the repository owner/name before using GraphQL:
bashrepo_json=$(gh repo view --json owner,name) owner=$(jq -r '.owner.login // .owner.name' <<<"$repo_json") repo=$(jq -r '.name' <<<"$repo_json")
Use GraphQL for unresolved review threads. Include pageInfo; omit cursor on the first page, then pass the previous endCursor with -f cursor="$cursor" while hasNextPage is true.
bashgh api graphql \ -f query='query($owner:String!,$repo:String!,$number:Int!,$cursor:String){repository(owner:$owner,name:$repo){pullRequest(number:$number){reviewThreads(first:100,after:$cursor){pageInfo{hasNextPage endCursor}nodes{id,isResolved,isOutdated,path,line,comments(last:1){nodes{author{login},body,createdAt,url}}}}}}}' \ -f owner="$owner" -f repo="$repo" -F number=<number>
Use this loop when a PR may have many review threads:
bashthread_query='query($owner:String!,$repo:String!,$number:Int!,$cursor:String){repository(owner:$owner,name:$repo){pullRequest(number:$number){reviewThreads(first:100,after:$cursor){pageInfo{hasNextPage endCursor}nodes{id,isResolved,isOutdated,path,line,comments(last:1){nodes{author{login},body,createdAt,url}}}}}}}' cursor_args=() while :; do page=$(gh api graphql -f query="$thread_query" -f owner="$owner" -f repo="$repo" -F number=<number> "${cursor_args[@]}") printf '%s\n' "$page" | jq -r '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved==false) | [.id,.path,(.line//""),(.isOutdated|tostring),(.comments.nodes[-1].author.login//""),(.comments.nodes[-1].body|gsub("\n";" ")|.[0:240])] | @tsv' jq -e '.data.repository.pullRequest.reviewThreads.pageInfo.hasNextPage' >/dev/null <<<"$page" || break cursor=$(jq -r '.data.repository.pullRequest.reviewThreads.pageInfo.endCursor' <<<"$page") cursor_args=(-f cursor="$cursor") done
Filter unresolved threads with jq:
bashjq -r '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved==false) | [.id,.path,(.line//""),(.isOutdated|tostring),(.comments.nodes[-1].author.login//""),(.comments.nodes[-1].body|gsub("\n";" ")|.[0:240])] | @tsv'
Resolve a stale thread only when the fix is verified:
bashgh api graphql \ -f query='mutation($threadId:ID!){resolveReviewThread(input:{threadId:$threadId}){thread{id,isResolved}}}' \ -f threadId=<thread-id>
git status.| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-03 | fail→fail | 3,133 | 4,187 | +34% | 1 | 1 | 0% | 411 | 1,355 | +230% | 0 | 0 | — |
case-01 | fail→fail | 6,034 | 4,659 | -23% | 1 | 1 | 0% | 331 | 1,341 | +305% | 0 | 0 | — |
case-02 | fail→fail | 4,540 | 3,714 | -18% | 1 | 1 | 0% | 165 | 1,300 | +688% | 0 | 0 | — |
case-04 | fail→fail | 3,424 | 3,653 | +7% | 1 | 1 | 0% | 337 | 1,310 | +289% | 0 | 0 | — |
case-05 | fail→fail | 6,925 | 4,255 | -39% | 1 | 1 | 0% | 1,289 | 1,302 | +1% | 0 | 0 | — |
case-06 | pass→fail | 3,996 | 5,007 | +25% | 1 | 1 | 0% | 850 | 1,304 | +53% | 0 | 0 | — |
case-07 | pass→pass | 8,937 | 4,328 | -52% | 1 | 1 | 0% | 1,803 | 1,969 | +9% | 0 | 0 | — |
case-08 | pass→pass | 8,654 | 6,608 | -24% | 1 | 1 | 0% | 1,674 | 1,871 | +12% | 0 | 0 | — |
case-09 | pass→pass | 4,998 | 3,726 | -25% | 1 | 1 | 0% | 1,182 | 1,962 | +66% | 0 | 0 | — |
case-10 | pass→pass | 4,815 | 2,460 | -49% | 1 | 1 | 0% | 1,010 | 1,554 | +54% | 0 | 0 | — |
case-11 | pass→pass | 3,091 | 2,092 | -32% | 1 | 1 | 0% | 637 | 1,617 | +154% | 0 | 0 | — |
case-12 | pass→pass | 17,227 | 3,839 | -78% | 1 | 1 | 0% | 1,877 | 1,835 | -2% | 0 | 0 | — |
case-13 | pass→pass | 7,977 | 3,656 | -54% | 1 | 1 | 0% | 1,390 | 1,844 | +33% | 0 | 0 | — |
case-14 | pass→pass | 4,631 | 2,609 | -44% | 1 | 1 | 0% | 871 | 1,728 | +98% | 0 | 0 | — |
case-15 | fail→fail | 6,344 | 2,301 | -64% | 1 | 1 | 0% | 1,134 | 1,614 | +42% | 0 | 0 | — |
case-16 | pass→fail | 11,054 | 3,642 | -67% | 1 | 1 | 0% | 2,201 | 1,778 | -19% | 0 | 0 | — |
case-17 | pass→pass | 5,967 | 4,322 | -28% | 1 | 1 | 0% | 1,039 | 1,921 | +85% | 0 | 0 | — |
case-18 | pass→pass | 4,346 | 2,632 | -39% | 1 | 1 | 0% | 783 | 1,666 | +113% | 0 | 0 | — |
case-19 | fail→fail | 7,866 | 3,587 | -54% | 1 | 1 | 0% | 1,475 | 1,833 | +24% | 0 | 0 | — |
case-20 | fail→pass | 9,002 | 4,258 | -53% | 1 | 1 | 0% | 1,717 | 1,809 | +5% | 0 | 0 | — |
case-21 | pass→pass | 9,025 | 3,075 | -66% | 1 | 1 | 0% | 1,743 | 1,648 | -5% | 0 | 0 | — |
case-22 | fail→fail | 11,404 | 6,517 | -43% | 1 | 1 | 0% | 1,886 | 2,309 | +22% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 16 counted toward the lift figure. The other 6 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of -5 percentage points is the difference between those two pass rates over the 16 comparable cases. 4 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.