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.
Respond to Copilot and human PR reviewer comments: evaluate feedback, fix sensible requests, ask about ambiguity, verify, commit, push, reply to threads, resolve addressed comments, and summarize…
Install Respond To Review Comments
$ npx skills add sillsdev/FieldWorks --skill respond-to-review-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sillsdev/FieldWorks respond-to-review-comments --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/sillsdev/FieldWorks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/respond-to-review-comments .claude/skills/respond-to-review-comments && 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 "respond-to-review-comments" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/respond-to-review-comments into .claude/skills/respond-to-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-review-comments", 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/sillsdev/FieldWorks/tree/main/.claude/skills/respond-to-review-commentsType 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 sillsdev/FieldWorks --skill respond-to-review-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sillsdev/FieldWorks respond-to-review-comments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/respond-to-review-comments .agents/skills/respond-to-review-comments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "respond-to-review-comments" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/respond-to-review-comments into .agents/skills/respond-to-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-review-comments", 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 sillsdev/FieldWorks --skill respond-to-review-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sillsdev/FieldWorks respond-to-review-comments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/respond-to-review-comments .cursor/skills/respond-to-review-comments && 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 "respond-to-review-comments" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/respond-to-review-comments into .cursor/skills/respond-to-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-review-comments", 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/sillsdev/FieldWorks.git --path .claude/skills/respond-to-review-comments--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 sillsdev/FieldWorks --skill respond-to-review-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sillsdev/FieldWorks respond-to-review-comments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/respond-to-review-comments .gemini/skills/respond-to-review-comments && 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 "respond-to-review-comments" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/respond-to-review-comments into .gemini/skills/respond-to-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-review-comments", 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 sillsdev/FieldWorks respond-to-review-commentsInstalls 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 sillsdev/FieldWorks --skill respond-to-review-comments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/respond-to-review-comments .github/skills/respond-to-review-comments && 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 "respond-to-review-comments" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/respond-to-review-comments into .github/skills/respond-to-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-review-comments", 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 sillsdev/FieldWorks --skill respond-to-review-comments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sillsdev/FieldWorks respond-to-review-comments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/respond-to-review-comments .opencode/skills/respond-to-review-comments && 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 "respond-to-review-comments" agent skill from https://github.com/sillsdev/FieldWorks/tree/main/.claude/skills/respond-to-review-comments into .opencode/skills/respond-to-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-to-review-comments", 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
respond-to-review-comments- GitHub stars
- 110
- Token cost
- ~2k tokens
- SKILL.md length
- 1,028 words
- Files
- 1
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Respond to Copilot and human PR reviewer comments: evaluate feedback, fix sensible requests, ask about ambiguity, verify, commit, push, reply to threads, resolve addressed comments, and summarize…
- Works in 4 steps: Load CONTEXT.md and apply the shared… → Load the repo instructions relevant to… → Use the grill-with-docs discipline for… → …
- Handling review comments
- SKILL.md covers Goals, Required Context, Comment Intake and Classify Each Comment, plus 6 more sections
- Calls git
What it does
Respond To Review Comments is an agent skill from sillsdev/FieldWorks. Respond to Copilot and human PR reviewer comments: evaluate feedback, fix sensible requests, ask about ambiguity, verify, commit, push, reply to threads, resolve addressed comments, and summarize results. Use when handling review comments, Copilot review feedback, requested changes, unresolved PR threads, or reviewer follow-up.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with GitHub. The repository describes itself as: FieldWorks is a suite of software tools for language and cultural data, with support for complex scripts.
When your agent uses it
- Handling review comments
- Copilot review feedback
- Requested changes
- Unresolved PR threads
Example prompts
- “/respond-to-review-comments”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Load CONTEXT.md and apply the shared language rules.
- Load the repo instructions relevant to touched files.
- Use the grill-with-docs discipline for ambiguous terminology: challenge fuzzy terms, ground terms in code, and update CONTEXT.md if the…
- Apply the code-review reception rule: verify feedback before implementing it.
What it can do on your machine
Read from SKILL.md and the folder at commit bd0608d. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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.
Context cost
Respond To Review Comments loads about 2k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 1,028 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); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,028 words (~1,996 tokens).
“Use this skill when the user wants a guided workflow for addressing Copilot or human reviewer comments on a FieldWorks pull request.”
- name
- respond-to-review-comments
- argument-hint
- Optional PR URL, reviewer name, comment ID, or focus area
Files
Just SKILL.md in .claude/skills/respond-to-review-comments of sillsdev/FieldWorks.
Open the folder on GitHubat commit bd0608d
Compare with similar skills
Respond To Review Comments 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 |
|---|---|---|---|---|---|---|
| Respond To Review Comments this skillsillsdev/FieldWorks | 110 | — | ~2k | Automated safety check: Pass | Custom licence | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Setup Matt Pocock Skillsbestofjs/bestofjs | 3.1k | 20 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT |
Similar skills
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
Setup Matt Pocock Skills
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
More from sillsdev/FieldWorks
All 29 skills in this repoAtlassian Readonly Skills
sillsdev/FieldWorks
Read-only Python utilities for Jira (SIL Data Center): fetch an issue, search with JQL, read transitions, links, worklogs, agile boards and projects.
Atlassian Skills
sillsdev/FieldWorks
Python utilities for Jira (SIL Data Center) covering issue management, JQL search, workflows and transitions, links, agile boards, worklogs and projects.
Fieldworks Winapp
sillsdev/FieldWorks
Control and document the FieldWorks desktop application with WinForms MCP or WinApp MCP.
Convert Slice
sillsdev/FieldWorks
Drive the conversion of one legacy slice type to the Avalonia detail view through analysis, developer alignment, integration-test planning, route/exemplar mapping, design, and scaffold/implement.
Dependabot Consolidation
sillsdev/FieldWorks
Combine several open Dependabot pull requests into a single branch and PR: enumerate the open Dependabot PRs, cherry-pick them onto fresh main, rewrite commit messages to satisfy…
Fieldworks Semantic Render Parity
sillsdev/FieldWorks
Capture or review FieldWorks parity evidence: semantic snapshots, render/visual baselines, layout parity, failure artifacts, XML view definitions, and the Avalonia presentation IR.
Related
Works with
Categories
Questions about Respond To Review Comments
What does Respond To Review Comments do?
Respond to Copilot and human PR reviewer comments: evaluate feedback, fix sensible requests, ask about ambiguity, verify, commit, push, reply to threads, resolve addressed comments, and summarize…. Respond To Review Comments is an agent skill from sillsdev/FieldWorks. Respond to Copilot and human PR reviewer comments: evaluate feedback, fix sensible requests, ask about ambiguity, verify, commit, push, reply to threads, resolve addressed comments, and summarize results.
When should I use Respond To Review Comments?
Respond To Review Comments fits situations like: handling review comments; copilot review feedback; requested changes; unresolved PR threads.
How do I install Respond To Review Comments in Claude Code?
Run `npx skills add sillsdev/FieldWorks --skill respond-to-review-comments -a claude-code`. Or copy the skill folder (.claude/skills/respond-to-review-comments in sillsdev/FieldWorks) into .claude/skills/respond-to-review-comments in your project. Claude Code loads it when a task matches its description.
How do I install Respond To Review Comments in Codex?
Run `npx skills add sillsdev/FieldWorks --skill respond-to-review-comments -a codex`. Or copy the skill folder (.claude/skills/respond-to-review-comments in sillsdev/FieldWorks) into .agents/skills/respond-to-review-comments in your project. Codex loads it when a task matches its description.
Can I use Respond To Review Comments 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 sillsdev/FieldWorks --skill respond-to-review-comments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/respond-to-review-comments, .gemini/skills/respond-to-review-comments, .github/skills/respond-to-review-comments and .opencode/skills/respond-to-review-comments in your project.
What does Respond To Review Comments need to run?
Going by SKILL.md and its folder, Respond To Review Comments needs the command-line tools its instructions call (git).
Does Respond To Review Comments access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Respond To Review Comments 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. Review the folder before installing.
What licence does Respond To Review Comments use?
Respond To Review Comments has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Respond To Review Comments use?
About 2k tokens (SKILL.md is roughly 8k 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 Respond To Review Comments?
Skills that share tags, products or a category with Respond To Review Comments: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Respond To Review Comments?
sillsdev (a GitHub organization) maintains it in sillsdev/FieldWorks, which has 110 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 8, 2026.
Source: sillsdev/FieldWorks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.