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.
Finds nacos.io doc files from GitHub Content Source URLs, resolves both zh-cn and en counterparts, applies feedback and maintainer suggestions with version-scoped edits.
Install Nacos Doc Feedback
$ npx skills add nacos-group/nacos-group.github.io --skill nacos-doc-feedback -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nacos-group/nacos-group.github.io nacos-doc-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/nacos-group/nacos-group.github.io.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nacos-doc-feedback .claude/skills/nacos-doc-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 "nacos-doc-feedback" agent skill from https://github.com/nacos-group/nacos-group.github.io/tree/develop-astro-nacos/.agents/skills/nacos-doc-feedback into .claude/skills/nacos-doc-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nacos-doc-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/nacos-group/nacos-group.github.io/tree/develop-astro-nacos/.agents/skills/nacos-doc-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 nacos-group/nacos-group.github.io --skill nacos-doc-feedback -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nacos-group/nacos-group.github.io nacos-doc-feedback --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nacos-group/nacos-group.github.io.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/nacos-doc-feedback .agents/skills/nacos-doc-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 "nacos-doc-feedback" agent skill from https://github.com/nacos-group/nacos-group.github.io/tree/develop-astro-nacos/.agents/skills/nacos-doc-feedback into .agents/skills/nacos-doc-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nacos-doc-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 nacos-group/nacos-group.github.io --skill nacos-doc-feedback -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nacos-group/nacos-group.github.io nacos-doc-feedback --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nacos-group/nacos-group.github.io.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/nacos-doc-feedback .cursor/skills/nacos-doc-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 "nacos-doc-feedback" agent skill from https://github.com/nacos-group/nacos-group.github.io/tree/develop-astro-nacos/.agents/skills/nacos-doc-feedback into .cursor/skills/nacos-doc-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nacos-doc-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/nacos-group/nacos-group.github.io.git --path .agents/skills/nacos-doc-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 nacos-group/nacos-group.github.io --skill nacos-doc-feedback -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nacos-group/nacos-group.github.io nacos-doc-feedback --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nacos-group/nacos-group.github.io.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/nacos-doc-feedback .gemini/skills/nacos-doc-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 "nacos-doc-feedback" agent skill from https://github.com/nacos-group/nacos-group.github.io/tree/develop-astro-nacos/.agents/skills/nacos-doc-feedback into .gemini/skills/nacos-doc-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nacos-doc-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 nacos-group/nacos-group.github.io nacos-doc-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 nacos-group/nacos-group.github.io --skill nacos-doc-feedback -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nacos-group/nacos-group.github.io.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/nacos-doc-feedback .github/skills/nacos-doc-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 "nacos-doc-feedback" agent skill from https://github.com/nacos-group/nacos-group.github.io/tree/develop-astro-nacos/.agents/skills/nacos-doc-feedback into .github/skills/nacos-doc-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nacos-doc-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 nacos-group/nacos-group.github.io --skill nacos-doc-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 nacos-group/nacos-group.github.io nacos-doc-feedback --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nacos-group/nacos-group.github.io.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/nacos-doc-feedback .opencode/skills/nacos-doc-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 "nacos-doc-feedback" agent skill from https://github.com/nacos-group/nacos-group.github.io/tree/develop-astro-nacos/.agents/skills/nacos-doc-feedback into .opencode/skills/nacos-doc-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nacos-doc-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
nacos-doc-feedback- GitHub stars
- 115
- Token cost
- ~793 tokens
- SKILL.md length
- 166 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Finds nacos.io doc files from GitHub Content Source URLs, resolves both zh-cn and en counterparts, applies feedback and maintainer suggestions with version-scoped edits.
- Works in 4 steps: 解析反馈块 → 确定要修改的文件 → 执行修改 → …
- The user pastes a feedback block containing 文档详细信息
- SKILL.md covers 输入格式识别, 工作流程, 路径与版本约定 and 示例, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Nacos Doc Feedback is an agent skill from nacos-group/nacos-group.github.io. Finds nacos.io doc files from GitHub Content Source URLs, resolves both zh-cn and en counterparts, applies feedback and maintainer suggestions with version-scoped edits. Use when the user pastes a feedback block containing "文档详细信息", "Content Source", or "nacos.io ➟ GitHub 问题链接".
Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `examples.md`).
It sits in Development. It works with GitHub. The repository describes itself as: nacos-group.github.io. The licence is Apache-2.0.
When your agent uses it
- The user pastes a feedback block containing 文档详细信息
- Nacos.io ➟ GitHub 问题链接
Example prompts
- “文档详细信息”
- “Content Source”
- “nacos.io ➟ GitHub 问题链接”
- “/nacos-doc-feedback”
Workflow steps
4 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 428cc2c. 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
No URLs in SKILL.md.
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
Nacos Doc Feedback loads about 793 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 166 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 nacos-group/nacos-group.github.io at commit 428cc2c, republished under its Apache-2.0 licence (© nacos-group). 166 words, ~793 tokens.
Download SKILL.mdSave it as
.claude/skills/nacos-doc-feedback/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- nacos-doc-feedback
- description
- Finds nacos.io doc files from GitHub Content Source URLs, resolves both zh-cn and en counterparts, applies feedback and maintainer suggestions with version-scoped edits. Use when the user pastes a feedback block containing "文档详细信息", "Content Source", or "nacos.io ➟ GitHub 问题链接".
Nacos 文档反馈处理
根据结构化反馈块，定位文档文件并按反馈与维护者建议修改内容。文档仓库根目录为 src/content/docs，结构为 {version}/{locale}/...（版本如 v3.0、next、latest，语言如 zh-cn、en）。
输入格式识别
反馈块通常包含三部分：
- 用户反馈：
[在此处输入反馈]下方的原始反馈内容。 - 文档详细信息（勿编辑）：含 Version ID、Content URL、Content Source（GitHub 文档源码 URL）、Service。
- Nacos维护者修改建议（可选）：指定修改范围或具体建议。
从 Content Source 提取本地路径：URL 中从 src/content 开始到末尾即为仓库内路径。例如：
https://github.com/nacos-group/nacos-group.github.io/tree/develop-astro-nacos/src/content/docs/v3.0/zh-cn/manual/admin/upgrading.mdx
→ 路径：src/content/docs/v3.0/zh-cn/manual/admin/upgrading.mdx
若 URL 带 blob 或只有路径片段，同样只保留从 src/content 起的部分。在当前工作区（nacos-group.github.io）下按该路径查找文件。
工作流程
1. 解析反馈块
- 提取用户反馈正文。
- 提取 Content Source，得到
src/content/docs/{version}/{locale}/...。 - 提取维护者修改建议（若有）：是否限定版本、是否限定语言、具体改法。
2. 确定要修改的文件
按 Content Source 找主文件
- 在仓库根下定位
src/content/docs/{version}/{locale}/...的完整路径，确认文件存在。
配对另一种语言
- 文档结构为
docs/{version}/{locale}/...，locale 为zh-cn或en。 - 同一版本、同一相对路径下，若存在另一 locale，则同时修改中英文：
- 当前为
zh-cn→ 再找同版本的en同路径文件并修改。 - 当前为
en→ 再找同版本的zh-cn同路径文件并修改。
- 当前为
- 若另一语言文件不存在（例如仅存在 zh-cn），则只改现有文件。
版本范围（重要）
- 维护者明确指定版本（如“只改 v3.0、next、latest”）：仅修改这些版本下的对应路径文件。
- 维护者未指定版本：
- 根据 Content Source 中的版本（如 v3.0）判断大版本（3.x）。
- 仅在同一大版本内查找其他版本（如 v3.0、next、latest 等）的同一相对路径；若存在且内容上存在相同问题，则同步修改。
- 不得修改其他大版本（如 2.x、1.x）的文档，除非维护者明确要求“同时修改 2.x”等。
3. 执行修改
- 根据用户反馈理解缺失或错误（如“未涉及客户端兼容性”“需补充 3.0.3 与 1.x/2.x 兼容说明”）。
- 优先遵循维护者修改建议（版本范围、是否只改部分版本、表述要求等）。
- 对每个选中的文件：读入内容 → 按反馈与建议编辑（增补、改写、统一表述）→ 写回。
- 中英文需语义一致，仅语言不同；若只改了一侧，务必同步另一侧。
4. 输出
- 列出本次修改的文件路径。
- 简要说明每处修改点（如“在 upgrading.mdx 中增加客户端兼容性说明”“同步到 en 与 v3.0/next/latest”）。
路径与版本约定
| 项目 | 说明 |
|---|---|
| 仓库根 | 工作区为 nacos-group.github.io，文档根为 src/content/docs。 |
| 版本目录 | 如 v3.0、v2.5、next、latest；大版本由主版本号区分（3.x、2.x）。 |
| 语言目录 | zh-cn、en，紧跟在版本目录下。 |
| 同文档 | 同一“文档”= 相同版本下相同相对路径（仅 locale 不同）。 |
示例
反馈块示例：
[在此处输入反馈]
升级文档中未涉及客户端兼容性情况，比如 3.0.3 服务版本是否兼容客户端 1.x 2.x
---
#### 文档详细信息
* Content Source: https://github.com/nacos-group/nacos-group.github.io/tree/develop-astro-nacos/src/content/docs/v3.0/zh-cn/manual/admin/upgrading.mdx
* Service: 用户指南/开发指南/运维指南
---
[Nacos维护者修改建议]
只需要添加 v3.0、next、latest 3 个版本的文档。处理步骤简述：
- 路径：
src/content/docs/v3.0/zh-cn/manual/admin/upgrading.mdx。 - 版本范围：仅 v3.0、next、latest（按维护者建议）。
- 文件集合：对 v3.0、next、latest 各取 zh-cn 与 en 的
manual/admin/upgrading.mdx（存在则加入）。 - 修改内容：在升级文档中增加客户端兼容性说明（如 3.0.3 与 1.x/2.x 兼容情况），中英文一致。
注意事项
- 不要修改反馈块中的“文档详细信息”部分。
- 大版本边界：3.x 反馈不自动改 2.x/1.x；2.x 反馈不自动改 3.x/1.x；除非维护者明确要求。
- 若某版本或某语言下无对应文件（路径不存在），跳过该组合，不创建新文件。
- 编辑时保持原有 frontmatter、标题层级和站内链接格式。
更多示例
路径解析与多版本/语言配对示例见 examples.md。
© nacos-group, Apache-2.0. 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 in .agents/skills/nacos-doc-feedback of nacos-group/nacos-group.github.io.
- SKILL.md
- examples.md
Open the folder on GitHubat commit 428cc2c
Compare with similar skills
Nacos Doc 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 |
|---|---|---|---|---|---|---|
| Nacos Doc Feedback this skillnacos-group/nacos-group.github.io | 115 | — | ~793 | Automated safety check: Pass | Apache-2.0 | |
| 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 nacos-group/nacos-group.github.io
Nacos API Doc Update
nacos-group/nacos-group.github.io
Updates Nacos API documentation from Swagger api.json. An agent skill from nacos-group/nacos-group.github.io.
Nacos Committer Update
nacos-group/nacos-group.github.io
Updates Nacos committer documentation and announcements in nacos-group.github.io.
Nacos Download Page
nacos-group/nacos-group.github.io
Updates Nacos download page and release history from a GitHub release URL.
Nacos Java Maintainer SDK
nacos-group/nacos-group.github.io
Updates Nacos Maintainer SDK documentation by comparing Maintainer Client interfaces with maintainer-sdk.md, then adding/removing APIs and overloads while preserving existing descriptions and…
Nacos Java SDK Doc
nacos-group/nacos-group.github.io
Updates Nacos Java SDK usage documentation by comparing Java Client interfaces with usage.md, then adding/removing APIs and overloads while preserving existing descriptions and examples.
Nacos Doc Sync En
nacos-group/nacos-group.github.io
Syncs Chinese (zh-cn) documentation changes to corresponding English (en) files.
Related
Works with
Categories
Questions about Nacos Doc Feedback
What does Nacos Doc Feedback do?
Finds nacos.io doc files from GitHub Content Source URLs, resolves both zh-cn and en counterparts, applies feedback and maintainer suggestions with version-scoped edits. io.io doc files from GitHub Content Source URLs, resolves both zh-cn and en counterparts, applies feedback and maintainer suggestions with version-scoped edits.
When should I use Nacos Doc Feedback?
Nacos Doc Feedback fits situations like: the user pastes a feedback block containing 文档详细信息; nacos.io ➟ GitHub 问题链接.
How do I install Nacos Doc Feedback in Claude Code?
Run `npx skills add nacos-group/nacos-group.github.io --skill nacos-doc-feedback -a claude-code`. Or copy the skill folder (.agents/skills/nacos-doc-feedback in nacos-group/nacos-group.github.io) into .claude/skills/nacos-doc-feedback in your project. Claude Code loads it when a task matches its description.
How do I install Nacos Doc Feedback in Codex?
Run `npx skills add nacos-group/nacos-group.github.io --skill nacos-doc-feedback -a codex`. Or copy the skill folder (.agents/skills/nacos-doc-feedback in nacos-group/nacos-group.github.io) into .agents/skills/nacos-doc-feedback in your project. Codex loads it when a task matches its description.
Can I use Nacos Doc 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 nacos-group/nacos-group.github.io --skill nacos-doc-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/nacos-doc-feedback, .gemini/skills/nacos-doc-feedback, .github/skills/nacos-doc-feedback and .opencode/skills/nacos-doc-feedback in your project.
What does Nacos Doc Feedback need to run?
SKILL.md names no scripts, command-line tools or credentials: Nacos Doc Feedback is instructions for the agent only.
Does Nacos Doc Feedback access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Nacos Doc 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 Nacos Doc Feedback use?
Nacos Doc Feedback is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nacos Doc Feedback use?
About 793 tokens (SKILL.md is roughly 3.2k 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 Nacos Doc Feedback?
Skills that share tags, products or a category with Nacos Doc Feedback: 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 Nacos Doc Feedback?
nacos-group (a GitHub organization) maintains it in nacos-group/nacos-group.github.io, which has 115 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 24, 2026.
Source: nacos-group/nacos-group.github.io on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.