PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Perform a thorough, read-only review of one GitHub pull request.
Install GitHub Code Review
$ npx skills add jackfranklin/dotfiles --skill github-code-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jackfranklin/dotfiles github-code-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/github-code-review .claude/skills/github-code-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "github-code-review" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/github-code-review into .claude/skills/github-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-code-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/github-code-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jackfranklin/dotfiles --skill github-code-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jackfranklin/dotfiles github-code-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude/skills/github-code-review .agents/skills/github-code-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-code-review" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/github-code-review into .agents/skills/github-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-code-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jackfranklin/dotfiles --skill github-code-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jackfranklin/dotfiles github-code-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude/skills/github-code-review .cursor/skills/github-code-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "github-code-review" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/github-code-review into .cursor/skills/github-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-code-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jackfranklin/dotfiles.git --path claude/skills/github-code-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jackfranklin/dotfiles --skill github-code-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jackfranklin/dotfiles github-code-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude/skills/github-code-review .gemini/skills/github-code-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "github-code-review" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/github-code-review into .gemini/skills/github-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-code-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jackfranklin/dotfiles github-code-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jackfranklin/dotfiles --skill github-code-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude/skills/github-code-review .github/skills/github-code-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "github-code-review" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/github-code-review into .github/skills/github-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-code-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jackfranklin/dotfiles --skill github-code-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jackfranklin/dotfiles github-code-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude/skills/github-code-review .opencode/skills/github-code-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "github-code-review" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/github-code-review into .opencode/skills/github-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-code-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
github-code-review- GitHub stars
- 255
- Token cost
- ~1.8k tokens
- SKILL.md length
- 690 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Perform a thorough, read-only review of one GitHub pull request.
- Works in 6 steps: Establish GitHub context → Read linked issues → Read all prior PR feedback → …
- Given a GitHub PR number and you need to understand its linked issue(s)
- SKILL.md covers Invocation and Workflow
- Calls gh, git and bash
What it does
GitHub Code Review is an agent skill from jackfranklin/dotfiles. Perform a thorough, read-only review of one GitHub pull request. Use when given a GitHub PR number and you need to understand its linked issue(s), all existing discussion and review feedback, and independently apply the code-review skill to the exact PR code.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts. Compatibility notes: Requires gh authenticated for the target repository, git, and a local clone of that repository.
It sits in Development, covering Code review. It works with GitHub. The repository describes itself as: My dotfiles for my dev environment, compromising of tmux, vim, zsh and git. The licence is MIT.
When your agent uses it
- Given a GitHub PR number and you need to understand its linked issue(s)
- All existing discussion and review feedback
- Independently apply the code-review skill to the exact PR code
Example prompts
- “/github-code-review”
Requirements
- Compatibility (from SKILL.md): Requires gh authenticated for the target repository, git, and a local clone of that repository.
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 7ec4998. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
ghgitbash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires gh authenticated for the target repository, git, and a local clone of that repository.
From compatibility in the SKILL.md frontmatter.
Context cost
GitHub Code Review loads about 1.8k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 690 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from jackfranklin/dotfiles at commit 7ec4998, republished under its MIT licence (© jackfranklin). 690 words, ~1,816 tokens.
Download SKILL.mdSave it as
.claude/skills/github-code-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- github-code-review
- description
- Perform a thorough, read-only review of one GitHub pull request. Use when given a GitHub PR number and you need to understand its linked issue(s), all existing discussion and review feedback, and independently apply the code-review skill to the exact PR code.
- compatibility
- Requires gh authenticated for the target repository, git, and a local clone of that repository.
- disable-model-invocation
- true
GitHub Code Review
Review exactly one GitHub pull request. This skill supplies GitHub context and
an isolated checkout; code-review remains the governing implementation
review standard. Be direct and evidence-based. Do not praise, approve, post
GitHub comments, modify the active checkout, or run tests unless the user
separately asks.
Invocation
/github-code-review 42Require one positive integer PR number. If it is missing or invalid, ask for it. Do not review every open PR as a fallback.
Workflow
1. Establish GitHub context
From the repository containing the active checkout, collect the PR metadata
and its patch. Use the explicit repository argument in later gh commands so
changing directories cannot change the target repository.
repo="$(gh repo view --json nameWithOwner --jq .nameWithOwner)"
gh pr view <number> -R "$repo" --json number,title,url,body,state,author,baseRefName,baseRefOid,headRefName,headRefOid,commits,files,additions,deletions,changedFiles,closingIssuesReferences,comments,reviews
gh pr diff <number> -R "$repo" --patchRead the title and body before inspecting the implementation. Identify the claimed problem, expected outcome, scope, and any unstated assumptions. A missing or vague description is relevant context, but is not automatically a blocking finding.
2. Read linked issues
Use the structured closingIssuesReferences returned by the PR metadata. Read
every linked issue, including its title, body, state, labels, and comments:
gh issue view <issue-url> --json number,title,url,state,labels,body,commentsA closing reference is authoritative; do not guess linked issues by grepping
arbitrary #123 text in prose. If no issues are linked, report that limitation
rather than inventing one.
3. Read all prior PR feedback
Read all three categories of feedback:
- PR conversation comments (
commentsfromgh pr view); - submitted reviews and their bodies (
reviewsfromgh pr view); - inline review threads, including their resolved and outdated state.
For inline threads, query GitHub's reviewThreads GraphQL connection. Request
the thread path, current/original line, isResolved, isOutdated, and every
comment's author, body, URL, and timestamp:
owner="${repo%%/*}"
name="${repo##*/}"
query='query($owner: String!, $name: String!, $number: Int!, $cursor: String) {
repository(owner: $owner, name: $name) {
pullRequest(number: $number) {
reviewThreads(first: 100, after: $cursor) {
nodes {
isResolved isOutdated path line originalLine
comments(first: 100) {
nodes { author { login } body url createdAt }
}
}
pageInfo { hasNextPage endCursor }
}
}
}
}'
gh api graphql -f query="$query" -F owner="$owner" -F name="$name" -F number=<number>Use each returned endCursor in the next request until hasNextPage is false.
Do not substitute the REST pull-request-comments endpoint: it cannot reliably
report thread resolution state.
Treat existing feedback as input to verify, not as conclusions to repeat. For each substantive concern, classify it as one of:
- Still open — the current PR still has the problem.
- Resolved — the current code addresses it.
- Stale or not applicable — the code changed, the thread is outdated, or the concern is unsupported by the current implementation.
- Needs author decision — it is a product or design question that cannot be settled from the code and issue.
Show full SKILL.md (325 more words)Show less
4. Create an isolated PR worktree
Review the actual PR head in a temporary detached Git worktree, never in the
user's active checkout. First obtain the PR's baseRefName from step 1, then
invoke the skill's trusted helper. It owns the temporary refs, worktree, state,
and cleanup lifecycle:
bash /home/jack/.claude/skills/github-code-review/scripts/github-code-review-worktree \
start <number> <baseRefName-from-step-1> originIt prints WORKTREE, BASE_REF, HEAD_REF, and STATE_FILE. Preserve all
four values. Use git -C "$WORKTREE" ... for every worktree command: each Bash
tool call starts from the active checkout, so cd in a previous call does not
persist. Do not recreate this logic in an inline shell script.
If origin is not the GitHub remote for the PR, identify the matching remote
first and pass its name as the optional final argument. If setup fails, explain
the failure and do not silently review the active checkout instead. Always
request cleanup when the review is finished or cannot continue:
bash /home/jack/.claude/skills/github-code-review/scripts/github-code-review-worktree \
finish "$STATE_FILE"Never use git checkout, git switch, git reset, git stash, git clean,
or gh pr checkout in the active checkout. The temporary refs and worktree
must be removed through the helper's finish command even if the review cannot
finish.
5. Perform the implementation review
Load and apply the sibling code-review skill now.
It defines the review principles and full implementation checklist. For its
context/diff step, use the isolated worktree and this exact PR range instead
of staged or unstaged changes:
git diff "$base_ref...HEAD"Read relevant unchanged code in the worktree: callers, types, constants, existing utilities, tests, and local repository instructions. Review the code independently; prior reviewer comments may guide investigation but never replace it.
6. Report
Use this format. Findings must identify a current location where possible, explain the concrete consequence, and recommend a correction. Do not duplicate existing feedback as a new finding; cross-reference it under existing feedback instead.
# GitHub Code Review — PR #<number>: <title>
## Intent
- PR: <your concise interpretation of the PR's intended change>
- Linked issue(s): <issue number/title and relevant acceptance criteria, or none>
- Scope assessed: <notable files or areas>
## Existing feedback reconciled
- **Still open** — <author and concern> (`path:line`)
- **Resolved** — <author and concern>
- **Stale or not applicable** — <author and reason>
- **Needs author decision** — <question>
## New findings
### Critical
- `path:line` — <problem, consequence, and correction>
### Important
- `path:line` — <problem, consequence, and correction>
### Minor
- `path:line` — <problem, consequence, and correction>
## Review limits
- <only genuine limitations, such as no linked issue or unavailable content>Omit empty severity sections. If no new findings exist, say No new findings.
Do not claim that the PR is mergeable or approved: the output is a thorough
code review, not a merge-decision shortcut.
© jackfranklin, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in claude/skills/github-code-review of jackfranklin/dotfiles.
- SKILL.md
- scripts/github-code-review-worktree
Open the folder on GitHubat commit 7ec4998
Compare with similar skills
GitHub Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| GitHub Code Review this skilljackfranklin/dotfiles | 255 | — | ~1.8k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| GitHub Review Iterationprisma/orm | 48k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| PR Finalize Reviewmicrosoft/garnet | 12k | — | ~3.1k | Automated safety check: Pass | MIT | |
| PR Review State Fetchprisma/orm | 48k | — | ~767 | Automated safety check: Pass | Apache-2.0 | |
| Fastlane Pull Request Reviewfastlane/fastlane | 42k | — | ~550 | Automated safety check: Pass | MIT |
Similar skills
- Official
GitHub Review Iteration
prisma/orm
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
- Official
PR Finalize Review
microsoft/garnet
Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.
- Official
PR Review State Fetch
prisma/orm
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
Fastlane Pull Request Review
fastlane/fastlane
Reviews a fastlane pull request against its linked issue and the project guides, separating blocking from non-blocking findings and handling vulnerabilities privately.
Pull Request Reviewer for daisyUI
saadeghi/daisyui
Reviews open pull requests in the daisyUI repository using read-only GitHub data and isolated base-versus-PR checks, then writes a merge verdict report.
More from jackfranklin/dotfiles
All 19 skills in this repoAdr
jackfranklin/dotfiles
Capture an Architecture Decision Record (ADR) for a significant decision made in the current project.
Jack References
jackfranklin/dotfiles
Manage Jack's personal technical reference library at ~/git/references.
Later
jackfranklin/dotfiles
Log items to come back to later — bugs found mid-task, feature ideas, project feedback — as GitHub Issues.
New Deno App
jackfranklin/dotfiles
Scaffold a new Deno 2 + Hono + Deno KV + Eta + HTMX app with password auth and PWA support.
Resolve Merge Conflict
jackfranklin/dotfiles
A skill your agent uses when you need to resolve an in-progress git merge/rebase conflict.
Writing Great Skills
jackfranklin/dotfiles
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Related
Works with
Categories
Questions about GitHub Code Review
What does GitHub Code Review do?
Perform a thorough, read-only review of one GitHub pull request. GitHub Code Review is an agent skill from jackfranklin/dotfiles. Perform a thorough, read-only review of one GitHub pull request.
When should I use GitHub Code Review?
GitHub Code Review fits situations like: given a GitHub PR number and you need to understand its linked issue(s); all existing discussion and review feedback; independently apply the code-review skill to the exact PR code.
How do I install GitHub Code Review in Claude Code?
Run `npx skills add jackfranklin/dotfiles --skill github-code-review -a claude-code`. Or copy the skill folder (claude/skills/github-code-review in jackfranklin/dotfiles) into .claude/skills/github-code-review in your project. Claude Code loads it when a task matches its description.
How do I install GitHub Code Review in Codex?
Run `npx skills add jackfranklin/dotfiles --skill github-code-review -a codex`. Or copy the skill folder (claude/skills/github-code-review in jackfranklin/dotfiles) into .agents/skills/github-code-review in your project. Codex loads it when a task matches its description.
Can I use GitHub Code Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jackfranklin/dotfiles --skill github-code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-code-review, .gemini/skills/github-code-review, .github/skills/github-code-review and .opencode/skills/github-code-review in your project.
What does GitHub Code Review need to run?
Going by SKILL.md and its folder, GitHub Code Review needs the command-line tools its instructions call (gh, git and bash). Compatibility (from SKILL.md): Requires gh authenticated for the target repository, git, and a local clone of that repository..
Does GitHub Code Review access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is GitHub Code Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does GitHub Code Review use?
GitHub Code Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does GitHub Code Review use?
About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to GitHub Code Review?
Skills that share tags, products or a category with GitHub Code Review: PR Babysitter (openinterpreter/openinterpreter, 69k stars), GitHub Review Iteration (prisma/orm, 48k stars), PR Finalize Review (microsoft/garnet, 12k stars) and PR Review State Fetch (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub Code Review?
jackfranklin (a GitHub user) maintains it in jackfranklin/dotfiles, which has 255 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.
Source: jackfranklin/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.