القائمة
Monitor a pull request through review and CI. Use when the user asks to monitor, watch, or babysit a PR.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/akornmeier/clawd-config --skill babysit-prيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
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".
| 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.