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.
A skill your agent uses when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving disagreements, or summarizing updates.
Install Engineering Review Feedback
$ npx skills add agentara/skills --skill engineering-review-feedback -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agentara/skills engineering-review-feedback --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/agentara/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/engineering/engineering-review-feedback .claude/skills/engineering-review-feedback && 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 "engineering-review-feedback" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-feedback into .claude/skills/engineering-review-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-review-feedback", 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/agentara/skills/tree/main/skills/engineering/engineering-review-feedbackType 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 agentara/skills --skill engineering-review-feedback -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agentara/skills engineering-review-feedback --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentara/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/engineering/engineering-review-feedback .agents/skills/engineering-review-feedback && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "engineering-review-feedback" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-feedback into .agents/skills/engineering-review-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-review-feedback", 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 agentara/skills --skill engineering-review-feedback -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agentara/skills engineering-review-feedback --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentara/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/engineering/engineering-review-feedback .cursor/skills/engineering-review-feedback && 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 "engineering-review-feedback" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-feedback into .cursor/skills/engineering-review-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-review-feedback", 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/agentara/skills.git --path skills/engineering/engineering-review-feedback--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 agentara/skills --skill engineering-review-feedback -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agentara/skills engineering-review-feedback --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentara/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/engineering/engineering-review-feedback .gemini/skills/engineering-review-feedback && 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 "engineering-review-feedback" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-feedback into .gemini/skills/engineering-review-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-review-feedback", 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 agentara/skills engineering-review-feedbackInstalls 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 agentara/skills --skill engineering-review-feedback -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agentara/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/engineering/engineering-review-feedback .github/skills/engineering-review-feedback && 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 "engineering-review-feedback" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-feedback into .github/skills/engineering-review-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-review-feedback", 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 agentara/skills --skill engineering-review-feedback -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agentara/skills engineering-review-feedback --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentara/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/engineering/engineering-review-feedback .opencode/skills/engineering-review-feedback && 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 "engineering-review-feedback" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-feedback into .opencode/skills/engineering-review-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-review-feedback", 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
engineering-review-feedback- GitHub stars
- 600
- Token cost
- ~1k tokens
- SKILL.md length
- 385 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving disagreements, or summarizing updates.
- Works in 6 steps: Pause before responding if the comment… → Identify what the reviewer is asking for. → Classify each comment → …
- Handling code review feedback as the change author
- SKILL.md covers Response Workflow, When You Agree, When You Need Clarification and When You Disagree, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Engineering Review Feedback is an agent skill from agentara/skills. Use when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving disagreements, or summarizing updates. TRIGGER on "address review feedback", "respond to this review comment", "reviewer asked", "I disagree with reviewer", "what should I reply?", or "apply PR comments". If role is unclear, ask reviewer or author. DO NOT TRIGGER for reviewer comment writing, full code review, or PR descriptions unless author-response behavior is requested.
Its SKILL.md is about 1k 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, covering Pull requests and Code review. The repository describes itself as: Original and practical skills for AI builders. The licence is MIT.
When your agent uses it
- Handling code review feedback as the change author
- Addressing reviewer comments
- Drafting replies
- Resolving disagreements
Example prompts
- “address review feedback”
- “respond to this review comment”
- “reviewer asked”
- “/engineering-review-feedback”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Pause before responding if the comment feels frustrating.
- Identify what the reviewer is asking for.
- Classify each comment
- Prefer improving the artifact over explaining in the review tool.
- Run the relevant verification.
- Reply with what changed, why, and how it was tested.
What it can do on your machine
Read from SKILL.md and the folder at commit 950e1bf. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
google.github.io
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
Engineering Review Feedback loads about 1k tokens when it runs. Until then it costs about 131 tokens; SKILL.md has 385 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
The full file from agentara/skills at commit 950e1bf, republished under its MIT licence (© agentara). 385 words, ~1,029 tokens.
Download SKILL.mdSave it as
.claude/skills/engineering-review-feedback/SKILL.md (or your agent's skills folder).- name
- engineering-review-feedback
- description
- Use when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving disagreements, or summarizing updates. TRIGGER on "address review feedback", "respond to this review comment", "reviewer asked", "I disagree with reviewer", "what should I reply?", or "apply PR comments". If role is unclear, ask reviewer or author. DO NOT TRIGGER for reviewer comment writing, full code review, or PR descriptions unless author-response behavior is requested.
Engineering Review Feedback
Handle reviewer feedback as collaboration toward better code. The best response often changes the code, tests, or comments so future readers benefit, rather than explaining only inside the review thread.
Adapted from Google Engineering Practices Documentation, especially "How to handle reviewer comments." Source: https://google.github.io/eng-practices/review/developer/handling-comments.html. License: CC-BY 3.0.
Response Workflow
- Pause before responding if the comment feels frustrating.
- Identify what the reviewer is asking for.
- Classify each comment:
- Code change required.
- Test change required.
- Documentation or comment change required.
- Clarification needed.
- Disagreement to discuss.
- Non-blocking suggestion.
- Prefer improving the artifact over explaining in the review tool.
- Run the relevant verification.
- Reply with what changed, why, and how it was tested.
If a reviewer says they do not understand the code, first try to make the code clearer. Add a code comment only when the why cannot be expressed cleanly in code.
When You Agree
Use a short response and make the change.
Done. I renamed the helper to describe normalization rather than validation and updated the two call sites.
Tested with: npm test -- user-profile.test.tsWhen You Need Clarification
Ask for the missing decision or constraint. Avoid defensive wording.
I want to make sure I understand the concern. Are you asking for this to reject duplicate requests at the API boundary, or for the worker to make duplicate processing idempotent?When You Disagree
Disagree by comparing tradeoffs, not by rejecting the person.
I chose X because it keeps the retry policy in one place and avoids a second queue state. My concern with Y is that it makes cancellation observable in two different layers.
If you think Y better serves the rollback requirement, I can switch to it. Is that the tradeoff you want prioritized?If the reviewer provides better technical reasoning, accept it and adjust. If neither side can converge, move to a higher-bandwidth conversation and summarize the decision back in the review.
Show full SKILL.md (170 more words)Show less
When Feedback Is Not Constructive
Do not reply in kind. Extract any technical concern that can be addressed in code, tests, or docs. If the comment is hostile, vague, or repeatedly unproductive, move to a private or higher-bandwidth conversation, involve a lead when needed, and summarize only the technical decision back in the review.
Fix the Right Place
- Confusing expression: simplify or rename it.
- Hidden invariant: encode it in types, validation, assertions, or a focused comment.
- Missing behavior confidence: add or improve tests.
- Missing context: update the PR description, code comment, README, or design doc.
- Reviewer misunderstanding caused by stale diff: rebase, remove dead code, or update the description.
- Pure preference: ask whether it is required; otherwise treat as optional.
Summary Reply Template
Addressed this round:
- Changed ...
- Added/updated tests for ...
- Clarified ...
Verification:
- `...`
Open:
- ...Common Mistakes
- Replying in anger or with sarcasm.
- Explaining confusing code only in the review thread.
- Treating every reviewer suggestion as mandatory without clarifying severity.
- Saying "will clean up later" when the current change introduces the complexity.
- Making broad unrelated refactors while addressing a narrow review comment.
© agentara, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/engineering/engineering-review-feedback of agentara/skills.
Open the folder on GitHubat commit 950e1bf
Compare with similar skills
Engineering Review Feedback 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 |
|---|---|---|---|---|---|---|
| Engineering Review Feedback this skillagentara/skills | 600 | — | ~1k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Open Code Review CLIalibaba/open-code-review | 44k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GitHub Review Iterationprisma/orm | 48k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
- 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.
Code Review
flutter/flutter
Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.
More from agentara/skills
All 20 skills in this repoWorld Cup Predictor
agentara/skills
Predict FIFA World Cup matches, full tournament paths, and champion probabilities through Codex-native subagents that analyze live news, weather, injuries, markets, Polymarket, tactics, and…
Presentation Design
agentara/skills
Generate a premium 6-slide presentation design board as one single composite image.
Publish Research Site
agentara/skills
Turn a thesis, proposition, trend, question, or explainer topic into a citation-backed, image-rich, interactive website and deploy it with Vercel CLI.
Portrait Clone
agentara/skills
Turn any n reference images (with at least one person) into one exhaustively locked, always de-slopped, JSON-only AIGC image prompt whose every variable is pinned so each generation is nearly…
Torn Paper Collage Poster
agentara/skills
Create AI image-generation prompts and image-generation workflows for torn-paper editorial collage style posters with layered ripped paper, rough typography, stamps, tape, stickers, cutout subjects…
Article To HTML
agentara/skills
Render a markdown draft / any document in the conversation context into a single-file "paper proposal" HTML — serif body, monospace meta, numbered sections, inline SVG figures, callouts, tables…
Related
Categories
Questions about Engineering Review Feedback
What does Engineering Review Feedback do?
A skill your agent uses when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving disagreements, or summarizing updates. Engineering Review Feedback is an agent skill from agentara/skills. Use when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving disagreements, or summarizing updates.
When should I use Engineering Review Feedback?
Engineering Review Feedback fits situations like: handling code review feedback as the change author; addressing reviewer comments; drafting replies; resolving disagreements.
How do I install Engineering Review Feedback in Claude Code?
Run `npx skills add agentara/skills --skill engineering-review-feedback -a claude-code`. Or copy the skill folder (skills/engineering/engineering-review-feedback in agentara/skills) into .claude/skills/engineering-review-feedback in your project. Claude Code loads it when a task matches its description.
How do I install Engineering Review Feedback in Codex?
Run `npx skills add agentara/skills --skill engineering-review-feedback -a codex`. Or copy the skill folder (skills/engineering/engineering-review-feedback in agentara/skills) into .agents/skills/engineering-review-feedback in your project. Codex loads it when a task matches its description.
Can I use Engineering Review Feedback 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 agentara/skills --skill engineering-review-feedback -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/engineering-review-feedback, .gemini/skills/engineering-review-feedback, .github/skills/engineering-review-feedback and .opencode/skills/engineering-review-feedback in your project.
What does Engineering Review Feedback need to run?
SKILL.md names no scripts, command-line tools or credentials: Engineering Review Feedback is instructions for the agent only.
Does Engineering Review Feedback access the network?
SKILL.md names 1 domain. As links in the text: google.github.io. This is read from the text; nothing was executed.
Is Engineering Review Feedback 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 Engineering Review Feedback use?
Engineering Review Feedback 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 Engineering Review Feedback use?
About 1k tokens (SKILL.md is roughly 4.1k 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 Engineering Review Feedback?
Skills that share tags, products or a category with Engineering Review Feedback: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars) and Open Code Review CLI (alibaba/open-code-review, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Engineering Review Feedback?
agentara (a GitHub organization) maintains it in agentara/skills, which has 600 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 29, 2026.
Source: agentara/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.