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.
Guides how an agent handles code review feedback: verify each suggestion against the codebase, ask about unclear items first, and push back with technical reasons when needed.
SKILL.md written in Chinese; this summary is our English description.
Install Receiving Code Review Feedback
$ npx skills add jnMetaCode/superpowers-zh --skill receiving-code-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jnMetaCode/superpowers-zh receiving-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/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/receiving-code-review .claude/skills/receiving-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 "receiving-code-review" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/receiving-code-review into .claude/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-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/jnMetaCode/superpowers-zh/tree/main/skills/receiving-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 jnMetaCode/superpowers-zh --skill receiving-code-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jnMetaCode/superpowers-zh receiving-code-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/receiving-code-review .agents/skills/receiving-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 "receiving-code-review" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/receiving-code-review into .agents/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-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 jnMetaCode/superpowers-zh --skill receiving-code-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jnMetaCode/superpowers-zh receiving-code-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/receiving-code-review .cursor/skills/receiving-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 "receiving-code-review" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/receiving-code-review into .cursor/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-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/jnMetaCode/superpowers-zh.git --path skills/receiving-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 jnMetaCode/superpowers-zh --skill receiving-code-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jnMetaCode/superpowers-zh receiving-code-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/receiving-code-review .gemini/skills/receiving-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 "receiving-code-review" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/receiving-code-review into .gemini/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-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 jnMetaCode/superpowers-zh receiving-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 jnMetaCode/superpowers-zh --skill receiving-code-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/receiving-code-review .github/skills/receiving-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 "receiving-code-review" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/receiving-code-review into .github/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-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 jnMetaCode/superpowers-zh --skill receiving-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 jnMetaCode/superpowers-zh receiving-code-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/receiving-code-review .opencode/skills/receiving-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 "receiving-code-review" agent skill from https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/receiving-code-review into .opencode/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-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
receiving-code-review- GitHub stars
- 8.3k
- Token cost
- ~707 tokens
- SKILL.md length
- 101 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guides how an agent handles code review feedback: verify each suggestion against the codebase, ask about unclear items first, and push back with technical reasons when needed.
- Review comments have arrived and are about to be applied to a branch
- SKILL.md covers 概述, 响应模式, 禁止的回应 and 处理不明确的反馈, plus 9 more sections
- Calls gh
- Feedback is ambiguous or technically doubtful and needs checking first
What it does
The skill is written in Chinese and treats review as technical evaluation, not social performance. The agent reads all feedback before reacting, restates the requirement, and checks each suggestion against the codebase before implementing it. Replies that praise the reviewer or announce instant implementation are ruled out; the agent states the technical point or simply acts.
If any item is unclear, the agent stops and asks about it before implementing anything, since items may be related. Feedback from your partner is trusted once understood, while feedback from external reviewers is checked for technical correctness in this codebase and for whether it would break existing behavior. A YAGNI check greps for real usage when a reviewer asks for a more complete feature, and the suggestion is dropped if nothing uses it.
Items are implemented one at a time with a test after each. The skill lists when to push back, such as a suggestion that breaks working code, lacks context, adds an unused feature, is wrong for the stack or conflicts with an architecture decision, and how to do it with technical reasoning. Correct feedback is acknowledged with a plain statement of the fix, a mistaken pushback is admitted briefly, and inline GitHub review comments are answered in their own thread.
When your agent uses it
- Review comments have arrived and are about to be applied to a branch
- Feedback is ambiguous or technically doubtful and needs checking first
- Replying to inline pull request review comments on GitHub
Example prompts
- “Go through the review comments on this PR, verify each against the code, and ask about anything unclear first.”
- “The reviewer wants the legacy code removed. Check whether anything still depends on it before acting.”
- “Reply to the inline review comments in their threads with what changed.”
Requirements
- The GitHub CLI (gh) for replying to review threads
What it can do on your machine
Read from SKILL.md and the folder at commit fe34019. 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:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, 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
Receiving Code Review Feedback loads about 707 tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 101 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 jnMetaCode/superpowers-zh at commit fe34019, republished under its MIT licence (© jnMetaCode). 101 words, ~707 tokens.
Download SKILL.mdSave it as
.claude/skills/receiving-code-review/SKILL.md (or your agent's skills folder).- name
- receiving-code-review
- description
- 收到代码审查反馈后、实施建议之前使用，尤其当反馈不明确或技术上有疑问时——需要技术严谨性和验证，而非敷衍附和或盲目执行
- version
- 1.0.0
- license
- MIT
接收代码审查
概述
代码审查需要的是技术评估，不是情绪表演。
核心原则： 先验证再实施。先提问再假设。技术正确性优先于社交舒适度。
响应模式
收到代码审查反馈时：
1. 阅读：完整阅读反馈，不急于反应
2. 理解：用自己的话复述需求（或提问）
3. 验证：对照代码库的实际情况检查
4. 评估：对这个代码库来说技术上合理吗？
5. 回应：技术性确认或有理有据的反驳
6. 实施：一次一项，逐个测试禁止的回应
绝不要说：
- "你说得太对了！"（明确违反 CLAUDE.md 规定）
- "好观点！"/"反馈很棒！"（敷衍表演）
- "让我立刻实施"（在验证之前）
应该这样做：
- 复述技术需求
- 提出澄清性问题
- 如果审查意见有误，用技术理由反驳
- 直接动手做（行动胜于言辞）
处理不明确的反馈
如果有任何一项不明确：
停下来——先不要实施任何内容
就不明确的项目提出澄清
为什么：各项之间可能有关联。部分理解 = 错误实施。示例：
搭档："修复第 1-6 项"
你理解 1、2、3、6。对 4、5 不确定。
❌ 错误做法：先实施 1、2、3、6，稍后再问 4、5
✅ 正确做法："第 1、2、3、6 项我理解了。第 4 和第 5 项需要澄清后再动手。"按来源区别处理
来自搭档的反馈
- 可信赖 —— 理解后直接实施
- 仍然要问 如果范围不明确
- 不要敷衍附和
- 直接行动 或给出技术性确认
来自外部审查者的反馈
实施之前：
1. 检查：对这个代码库来说技术上正确吗？
2. 检查：是否会破坏现有功能？
3. 检查：当前实现这样写是否有原因？
4. 检查：在所有平台/版本上都适用吗？
5. 检查：审查者了解完整上下文吗？
如果建议似乎有误：
用技术理由反驳
如果无法轻易验证：
说明情况："没有 [X] 我无法验证这一点。我应该 [调查/提问/先做]？"
如果与搭档之前的决策冲突：
先停下来和搭档讨论搭档的原则： "对外部反馈要持怀疑态度，但要仔细核实"
YAGNI 检查——针对"专业化"功能建议
如果审查者建议"正规地实现"：
在代码库中 grep 实际使用情况
如果没人用："这个接口没有被调用。删掉它（YAGNI）？"
如果有人用：那就正规实现搭档的原则： "你和审查者都对我负责。如果我们不需要这个功能，就不要加。"
实施顺序
对于包含多项的反馈：
1. 先澄清所有不明确的项
2. 然后按以下顺序实施：
- 阻塞性问题（崩溃、安全）
- 简单修复（拼写、导入）
- 复杂修复（重构、逻辑）
3. 逐个测试每项修复
4. 验证没有回归何时反驳
在以下情况反驳：
- 建议会破坏现有功能
- 审查者缺少完整上下文
- 违反 YAGNI（功能没人用）
- 对当前技术栈来说技术上不正确
- 存在遗留/兼容性原因
- 与搭档的架构决策冲突
如何反驳：
- 用技术理由，不要带防御情绪
- 提出具体问题
- 引用可正常工作的测试/代码
- 如果涉及架构问题，让搭档参与
如果觉得不方便当众反驳，暗号是： "Strange things are afoot at the Circle K"
确认正确的反馈
当反馈确实正确时：
✅ "已修复。[简要说明改了什么]"
✅ "发现得好——[具体问题]。已在 [位置] 修复。"
✅ [直接修复并在代码中体现]
❌ "你说得太对了！"
❌ "好观点！"
❌ "感谢你发现了这个！"
❌ "感谢你 [任何内容]"
❌ 任何感谢的表达为什么不用感谢： 行动说明一切。直接修复。代码本身就能表明你收到了反馈。
如果你发现自己要写"感谢"： 删掉它。直接说明修复内容。
优雅地纠正自己的反驳
如果你反驳了但事后发现自己错了：
✅ "你是对的——我检查了 [X]，确实 [Y]。正在实施。"
✅ "验证后确认你是对的。我最初的理解有误，因为 [原因]。正在修复。"
❌ 长篇道歉
❌ 为自己的反驳辩护
❌ 过度解释如实陈述纠正，然后继续。
常见错误
| 错误 | 修正 |
|---|---|
| 敷衍附和 | 复述需求或直接行动 |
| 盲目实施 | 先对照代码库验证 |
| 批量实施不测试 | 一次一项，逐个测试 |
| 假设审查者一定对 | 检查是否会破坏现有功能 |
| 回避反驳 | 技术正确性 > 社交舒适度 |
| 部分理解就开始实施 | 先澄清所有项 |
| 无法验证却继续推进 | 说明限制，请求指导 |
真实案例
敷衍附和（反面例子）：
审查者："删除遗留代码"
❌ "你说得太对了！让我删掉它……"技术验证（正面例子）：
审查者："删除遗留代码"
✅ "查了一下……构建目标是 10.15+，这个 API 需要 13+。向后兼容需要保留遗留代码。当前实现有错误的 bundle ID——修复它还是放弃 pre-13 支持？"YAGNI（正面例子）：
审查者："实现完善的指标追踪，包括数据库、日期过滤、CSV 导出"
✅ "在代码库中 grep 了一下——没有任何地方调用这个接口。删掉它（YAGNI）？还是有我遗漏的调用？"不明确的项（正面例子）：
搭档："修复第 1-6 项"
你理解 1、2、3、6。对 4、5 不确定。
✅ "第 1、2、3、6 项我理解了。第 4 和第 5 项需要澄清后再动手。"GitHub 评论回复
在 GitHub 上回复行内审查评论时，在评论线程中回复（gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies），不要发顶层 PR 评论。
© jnMetaCode, 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/receiving-code-review of jnMetaCode/superpowers-zh.
Open the folder on GitHubat commit fe34019
Compare with similar skills
Receiving Code 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 |
|---|---|---|---|---|---|---|
| Receiving Code Review Feedback this skilljnMetaCode/superpowers-zh | 8.3k | — | ~707 | 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 jnMetaCode/superpowers-zh
All 21 skills in this repoBrainstorming Before Building
jnMetaCode/superpowers-zh
Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.
Git Worktree Isolation
jnMetaCode/superpowers-zh
Sets up an isolated workspace before feature work or plan execution, preferring native worktree tools and falling back to git worktree, with instructions in Chinese.
Inline Plan Execution
jnMetaCode/superpowers-zh
Executes a written implementation plan task by task in the current session, with a progress ledger, test-first gates and one fresh-context review at the end.
Agency Orchestrator Workflow Runner
jnMetaCode/superpowers-zh
Runs agency-orchestrator YAML workflows inside the current agent session, with the session's own model playing each role in turn and no API key needed.
Chinese Code Review Etiquette
jnMetaCode/superpowers-zh
Gives Chinese-language templates and priority labels for code review feedback, plus guidance on bilingual comments, commit messages and common team anti-patterns.
Chinese Commit Conventions
jnMetaCode/superpowers-zh
Reference for Chinese-language git commits and changelogs: Conventional Commits adapted for Chinese teams, with templates, breaking-change notes and issue links for several platforms.
Related
Works with
Categories
Questions about Receiving Code Review Feedback
What does Receiving Code Review Feedback do?
Guides how an agent handles code review feedback: verify each suggestion against the codebase, ask about unclear items first, and push back with technical reasons when needed. The skill is written in Chinese and treats review as technical evaluation, not social performance. The agent reads all feedback before reacting, restates the requirement, and checks each suggestion against the codebase before implementing it.
When should I use Receiving Code Review Feedback?
Receiving Code Review Feedback fits situations like: review comments have arrived and are about to be applied to a branch; feedback is ambiguous or technically doubtful and needs checking first; replying to inline pull request review comments on GitHub.
How do I install Receiving Code Review Feedback in Claude Code?
Run `npx skills add jnMetaCode/superpowers-zh --skill receiving-code-review -a claude-code`. Or copy the skill folder (skills/receiving-code-review in jnMetaCode/superpowers-zh) into .claude/skills/receiving-code-review in your project. Claude Code loads it when a task matches its description.
How do I install Receiving Code Review Feedback in Codex?
Run `npx skills add jnMetaCode/superpowers-zh --skill receiving-code-review -a codex`. Or copy the skill folder (skills/receiving-code-review in jnMetaCode/superpowers-zh) into .agents/skills/receiving-code-review in your project. Codex loads it when a task matches its description.
Can I use Receiving Code 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 jnMetaCode/superpowers-zh --skill receiving-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/receiving-code-review, .gemini/skills/receiving-code-review, .github/skills/receiving-code-review and .opencode/skills/receiving-code-review in your project.
What does Receiving Code Review Feedback need to run?
Going by SKILL.md and its folder, Receiving Code Review Feedback needs the command-line tools its instructions call (gh). Our summary lists: The GitHub CLI (gh) for replying to review threads.
Does Receiving Code Review Feedback access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Receiving Code 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 Receiving Code Review Feedback use?
Receiving Code Review Feedback is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Receiving Code Review Feedback use?
About 707 tokens (SKILL.md is roughly 2.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 Receiving Code Review Feedback?
Skills that share tags, products or a category with Receiving Code Review Feedback: 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 Receiving Code Review Feedback?
jnMetaCode (a GitHub user) maintains it in jnMetaCode/superpowers-zh, which has 8,265 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 4, 2026.
Source: jnMetaCode/superpowers-zh on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.