babysit
thedotmack/claude-mem
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.
...Expand allAbout babysit
Watches a pull request or review cycle until it is genuinely ready to merge, continuing to check rather than stopping after a single pass while comments or review threads remain unresolved. The workflow identifies the PR number, branch, and base branch, confirms the PR is not a draft, and inspects mergeability, checks, the review decision, comments, and review threads. Pending checks are watched until they finish, polling at a practical interval of roughly 30 to 60 seconds unless the user requests a different cadence. New comments and unresolved review threads are read, with bot summaries treated as useful but actionable findings verified against the code.
Real issues are fixed in focused commits, relevant tests or builds are run, changes are pushed, and the cycle returns to re-inspecting status. Stale review threads are resolved only after verifying that the code or generated artifact now addresses the comment. The process stops only when checks are passing or intentionally skipped, the review decision is acceptable, no actionable comments remain, and no unresolved review threads remain.
The skill provides concrete GitHub CLI and GraphQL recipes. gh pr view with a JSON field list gives coarse status including state, draft status, mergeability, mergeStateStatus, reviewDecision, headRefOid, and statusCheckRollup. The repository owner and name are resolved with gh repo view and jq before GraphQL queries. Unresolved review threads are fetched with a reviewThreads GraphQL query that includes pageInfo for pagination, with a documented loop that pages through results using endCursor while hasNextPage is true and filters unresolved threads with jq. A resolveReviewThread mutation resolves a thread only when the fix is verified. Operating rules include keeping the watcher running during long checks, confirming whether bot-reported issues are against stale or current code, verifying that source and generated artifacts agree before resolving, doing a fresh final sweep, and reporting concrete evidence such as the latest commit SHA, check results, unresolved thread count, tests run, and any dirty local files.
FAQ
When does the skill stop watching a PR?
Only when checks are passing or intentionally skipped, the review decision is acceptable, no actionable comments remain, and no unresolved review threads remain. It does not stop after a single check pass if threads are still open.
How often does it poll for status?
At a practical interval, usually 30 to 60 seconds, unless the user asks for a different cadence. The watcher is kept running while long checks are still pending.
How are unresolved review threads found?
With a GraphQL reviewThreads query that includes pageInfo, paging through results using the previous endCursor while hasNextPage is true, then filtering threads where isResolved is false with jq.
When is it safe to resolve a stale review thread?
Only after verifying that the code or generated artifact now addresses the comment, using the resolveReviewThread mutation. For distributed generated files, the source and generated artifact must be confirmed to agree first.
What should be reported at the end?
Concrete evidence: the latest commit SHA, check names and results, the unresolved thread count, tests run, and any dirty local files left untouched, after doing one fresh sweep of PR status, threads, recent comments, and git status.
Stay with the PR until it is actually clean. Do not stop after one check pass if comments or review threads are still unresolved.
Workflow
- Identify the PR number, branch, and base branch.
- Confirm the PR is not draft and inspect mergeability, checks, review decision, comments, and review threads.
- Watch pending checks until they finish. Poll at a practical interval, usually 30-60 seconds unless the user asks for a different cadence.
- Read new comments and unresolved review threads. Treat bot summaries as useful, but verify actionable findings against the code.
- Fix real issues in focused commits, run relevant tests/builds, push, and return to step 2.
- Resolve stale review threads only after verifying the code or generated artifact now addresses the comment.
- Stop only when checks are passing or intentionally skipped, review decision is acceptable, no actionable comments remain, and no unresolved review threads remain.
GitHub CLI Checks
Use gh pr view for the coarse status:
gh pr view <number> --json \ number,state,isDraft,mergeable,mergeStateStatus,reviewDecision,headRefOid,statusCheckRollup,url
Resolve the repository owner/name before using GraphQL:
repo_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.
gh 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:
thread_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' "$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("";" ")|.[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:
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("";" ")|.[0:240])] | @tsv'
Resolve a stale thread only when the fix is verified:
gh api graphql \ -f query='mutation($threadId:ID!){resolveReviewThread(input:{threadId:$threadId}){thread{id,isResolved}}}' \ -f threadId=<thread-id>
Operating Rules
- Keep the watcher running while long checks are pending.
- If a generated file is part of the distribution, verify the source and generated artifact agree before resolving comments.
- If a bot reports an issue against stale code, confirm whether the thread is outdated or addressed in the latest head.
- Before final reporting, do one fresh sweep of PR status, unresolved threads, recent comments, and local
git status. - Report concrete evidence: latest commit SHA, check names and results, unresolved thread count, tests run, and any dirty local files left untouched.
All Files
0 filesInstall babysit
Download and extract the skill files to your .claude/skills/ directory.
Download ZIPClone the repository and copy the skill files to your project.
git clone https://github.com/thedotmack/claude-mem/blob/main/plugin/skills/babysit/SKILL.md # Copy SKILL.md to your .claude/skills/ directory
Copy





Home
