用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/akornmeier/clawd-config --skill babysit-pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
File a concise pull request. Use when the user asks to file, open, or create a PR.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui in React projects (Next.js, Vite, React Router), component registries, presets, --preset codes, or any React project with a components.json file. For Vue or Nuxt, use the shadcn-vue skill instead. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
Manages shadcn-vue components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn-vue in Vue or Nuxt projects, component registries, presets, --preset codes, or any Vue project with a components.json file. For React, use the shadcn skill instead. Also triggers for "shadcn-vue init", "create an app with --preset", or "switch to --preset".
基于 SOC 职业分类
正在显示 SKILL.md
| name | babysit-pr |
| description | Monitor a pull request through review and CI. Use when the user asks to monitor, watch, or babysit a PR. |
| metadata | {"harness":["claude","codex","pi"],"platform":["darwin"],"scope":"fleet"} |
All the repos we work in have various AI review bots. They're helpful, even if they are not always right.
If your harness offers tools to monitor a PR, use them so you can respond when comments arrive. Otherwise, poll the PR for new comments and checks.
Only act on checks and comments newer than the latest push. Verify every bot finding against the source before changing code. Fix real findings and CI failures, distinguish repository failures from infrastructure flakes, and reply with a written reason when dismissing false positives.
Keep an eye on changes to main and rebase when needed. If an overlapping PR makes this one obsolete, stop monitoring, report it to the user, and ask before closing the PR unless closure was explicitly authorized.
If a review bot leaves feedback you believe is not worth addressing, reply and resolve the comment. Format comments left on Tony's behalf as:
[MODEL-SLUG] RESPONDING ON BEHALF OF TONY
-----
[actual reply]
Screenshots and videos help as well — attach them when they make the feedback easier to act on.
Do not let the feedback expand the PR beyond the user's original goal. Address real shortcomings, but avoid scope creep.
If nothing has changed, stay quiet rather than posting filler comments. Stop when the review bots and required checks are green on the latest commit. Merge only when the user explicitly requested it; otherwise report that the PR is ready.