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 drafting, rewriting, classifying, or improving code review comments as a reviewer.
Install Engineering Review Comments
$ npx skills add agentara/skills --skill engineering-review-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agentara/skills engineering-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/agentara/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/engineering/engineering-review-comments .claude/skills/engineering-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 "engineering-review-comments" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-comments into .claude/skills/engineering-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-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/agentara/skills/tree/main/skills/engineering/engineering-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 agentara/skills --skill engineering-review-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agentara/skills engineering-review-comments --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-comments .agents/skills/engineering-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 "engineering-review-comments" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-comments into .agents/skills/engineering-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-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 agentara/skills --skill engineering-review-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agentara/skills engineering-review-comments --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-comments .cursor/skills/engineering-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 "engineering-review-comments" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-comments into .cursor/skills/engineering-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-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/agentara/skills.git --path skills/engineering/engineering-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 agentara/skills --skill engineering-review-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agentara/skills engineering-review-comments --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-comments .gemini/skills/engineering-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 "engineering-review-comments" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-comments into .gemini/skills/engineering-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-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 agentara/skills engineering-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 agentara/skills --skill engineering-review-comments -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-comments .github/skills/engineering-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 "engineering-review-comments" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-comments into .github/skills/engineering-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-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 agentara/skills --skill engineering-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 agentara/skills engineering-review-comments --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-comments .opencode/skills/engineering-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 "engineering-review-comments" agent skill from https://github.com/agentara/skills/tree/main/skills/engineering/engineering-review-comments into .opencode/skills/engineering-review-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-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
engineering-review-comments- GitHub stars
- 600
- Token cost
- ~1.1k tokens
- SKILL.md length
- 403 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting, rewriting, classifying, or improving code review comments as a reviewer.
- Works in 5 steps: Re-evaluate their argument first. They… → If they are right, say so plainly and… → If you still disagree, restate their… → …
- Improving code review comments as a reviewer
- SKILL.md covers Comment Shape, Severity Labels, Writing Rules and Wording Patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Engineering Review Comments is an agent skill from agentara/skills. Use when drafting, rewriting, classifying, or improving code review comments as a reviewer. TRIGGER on rough review notes, requests to make comments clearer or kinder, severity labels, "how should I phrase this review comment?", "write review comments", author pushback, or turning findings into PR comments. If role is unclear, ask reviewer or author. DO NOT TRIGGER for full code review, PR descriptions, or author responses unless wording is requested.
Its SKILL.md is about 1.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
- Improving code review comments as a reviewer
- Rough review notes
- Requests to make comments clearer
- Severity labels
Example prompts
- “how should I phrase this review comment?”
- “write review comments”
- “/engineering-review-comments”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Re-evaluate their argument first. They may be closer to the code or have context you missed.
- If they are right, say so plainly and resolve the comment.
- If you still disagree, restate their point, then explain the code-health reason for your request.
- Distinguish mandatory requests from preferences.
- If the thread stops making progress, move to a higher-bandwidth discussion and summarize the decision back in the review.
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.
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 Comments loads about 1.1k tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 403 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). 403 words, ~1,129 tokens.
Download SKILL.mdSave it as
.claude/skills/engineering-review-comments/SKILL.md (or your agent's skills folder).- name
- engineering-review-comments
- description
- Use when drafting, rewriting, classifying, or improving code review comments as a reviewer. TRIGGER on rough review notes, requests to make comments clearer or kinder, severity labels, "how should I phrase this review comment?", "write review comments", author pushback, or turning findings into PR comments. If role is unclear, ask reviewer or author. DO NOT TRIGGER for full code review, PR descriptions, or author responses unless wording is requested.
Engineering Review Comments
Review comments should improve the code and the developer's future judgment. They should be clear about severity, grounded in engineering reasoning, and directed at the code rather than the person.
Adapted from Google Engineering Practices Documentation, especially "How to write code review comments" and "Handling pushback in code reviews." Source: https://google.github.io/eng-practices/review/reviewer/comments.html. License: CC-BY 3.0.
Comment Shape
Use this structure for non-trivial comments:
SEVERITY: Observation about the code.
Why this matters: engineering reason, user impact, maintainability impact, or violated project rule.
Requested action: concrete fix, question, or decision the author needs to make.Keep tiny comments tiny. Use the full shape when intent could be misunderstood.
Severity Labels
BLOCKER: must change before approval because correctness, maintainability, security, data, test, or operational risk is unacceptable.IMPORTANT: should change before approval; can be waived only with an explicit rationale.QUESTION: reviewer needs information before deciding.NIT: minor polish. Do not block approval.OPTIONALorCONSIDER: a suggestion the author can decline.FYI: educational context or future consideration; no action expected.
Writing Rules
- Comment on the code, design, tests, or behavior; do not characterize the author.
- Explain why when asking for anything beyond obvious style or mechanical cleanup.
- Prefer "this makes X harder because..." over "I don't like X."
- Ask for simpler code when a review-thread explanation is needed to understand ordinary behavior.
- Accept a code comment only when the code cannot reasonably express the why by itself.
- Provide direct code or a specific design only when it is faster or safer than making the author infer it.
- Otherwise describe the problem and let the author choose the implementation.
- Point out good engineering choices when useful, and say why they are good.
Show full SKILL.md (152 more words)Show less
Wording Patterns
Use these patterns directly when helpful:
BLOCKER: This path can return success before the write is durable.
If the process crashes after this point, callers will believe the operation completed even though the data may be missing. Please either move the success response after the durable write or make the operation explicitly asynchronous and observable.QUESTION: What guarantees that this callback cannot run concurrently?
If it can run in parallel, `pending` can be decremented twice from the same value. If the framework serializes this callback, please add a short comment at the boundary where that guarantee comes from.NIT: This helper name reads as if it validates the payload, but it only normalizes whitespace. Could we rename it to `normalizePayloadText`?OPTIONAL: Consider extracting this branch into a named helper. The current version is correct, but a helper would make the three policy cases easier to scan.Handling Pushback
When the author disagrees:
- Re-evaluate their argument first. They may be closer to the code or have context you missed.
- If they are right, say so plainly and resolve the comment.
- If you still disagree, restate their point, then explain the code-health reason for your request.
- Distinguish mandatory requests from preferences.
- If the thread stops making progress, move to a higher-bandwidth discussion and summarize the decision back in the review.
Do not keep arguing because you wrote the first comment. The goal is the best code, not defending the initial wording.
Common Mistakes
- Leaving unlabeled comments that authors interpret as mandatory.
- Writing a correct critique in a tone that makes collaboration harder.
- Asking the author to explain confusing code only in the review tool.
- Turning every comment into a complete design assignment.
- Treating educational notes as blockers.
© 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-comments of agentara/skills.
Open the folder on GitHubat commit 950e1bf
Compare with similar skills
Engineering 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 |
|---|---|---|---|---|---|---|
| Engineering Review Comments this skillagentara/skills | 600 | — | ~1.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 Comments
What does Engineering Review Comments do?
A skill your agent uses when drafting, rewriting, classifying, or improving code review comments as a reviewer. Engineering Review Comments is an agent skill from agentara/skills. Use when drafting, rewriting, classifying, or improving code review comments as a reviewer.
When should I use Engineering Review Comments?
Engineering Review Comments fits situations like: improving code review comments as a reviewer; rough review notes; requests to make comments clearer; severity labels.
How do I install Engineering Review Comments in Claude Code?
Run `npx skills add agentara/skills --skill engineering-review-comments -a claude-code`. Or copy the skill folder (skills/engineering/engineering-review-comments in agentara/skills) into .claude/skills/engineering-review-comments in your project. Claude Code loads it when a task matches its description.
How do I install Engineering Review Comments in Codex?
Run `npx skills add agentara/skills --skill engineering-review-comments -a codex`. Or copy the skill folder (skills/engineering/engineering-review-comments in agentara/skills) into .agents/skills/engineering-review-comments in your project. Codex loads it when a task matches its description.
Can I use Engineering 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 agentara/skills --skill engineering-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/engineering-review-comments, .gemini/skills/engineering-review-comments, .github/skills/engineering-review-comments and .opencode/skills/engineering-review-comments in your project.
What does Engineering Review Comments need to run?
SKILL.md names no scripts, command-line tools or credentials: Engineering Review Comments is instructions for the agent only.
Does Engineering Review Comments 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 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 Engineering Review Comments use?
Engineering Review Comments 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 Comments use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Comments?
Skills that share tags, products or a category with Engineering Review Comments: 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 Comments?
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.