babysit-pr 是做什么的？
在 GitHub Pull Request 创建后持续监控其合并流程：定期轮询审阅评论、CI 检查/工作流运行以及可合并性状态，直到 PR 被合并/关闭或需要用户协助。技能会自动诊断失败原因，对疑似不稳定的失败最多重试 3 次，在适当的情况下自动修复/推送与分支相关的问题，并持续关注开放的 PR，以便及时呈现新的审阅反馈。当用户要求 Codex 监视 PR、观察 CI、处理审阅评论或留意开放 PR 上的失败和反馈时，请使用此技能。
持续监控 GitHub Pull Request 合并流程，自动诊断并重试故障，以及处理审核反馈。
该技能用于在 GitHub Pull Request 创建后自动“托管”其合并流程，通过持续轮询 GitHub API 来跟踪审阅评论、CI 检查、工作流运行以及 PR 的可合并性状态。当遇到 CI 失败时，它会自动诊断失败原因，并对疑似不稳定的失败进行最多 3 次重试。如果失败与分支相关问题有关（例如需要合并主分支），它会尝试自动修复并推送。这项技能对于希望减少手动检查 CI 结果和 PR 状态的开发工程师非常有用，能够显著提高开发效率。它适用于 Codex 平台，当用户明确要求“监视 PR”、“观察 CI”或“处理审阅评论”时，技能会自动启动并持续工作，直到 PR 被合并或关闭，或者遇到需要人工干预的情况。
npx skills add https://github.com/openai/codex/tree/main/skills/babysit-prInstalled? Explore more 生产力与协作 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
在 GitHub Pull Request 创建后持续监控其合并流程：定期轮询审阅评论、CI 检查/工作流运行以及可合并性状态，直到 PR 被合并/关闭或需要用户协助。技能会自动诊断失败原因，对疑似不稳定的失败最多重试 3 次，在适当的情况下自动修复/推送与分支相关的问题，并持续关注开放的 PR，以便及时呈现新的审阅反馈。当用户要求 Codex 监视 PR、观察 CI、处理审阅评论或留意开放 PR 上的失败和反馈时，请使用此技能。
This repo contains 19 individual skills — each has its own dedicated page.
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.
Run a final code review on a pull request
Change size guidance (800 lines)
Model visible context
Test authoring guidance
Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.
Run a GitHub issue digest for openai/codex by feature-area labels, all areas, and configurable time windows. Use when asked to summarize recent Codex bug reports or enhancement requests, especially for owner-specific labels such as tui, exec, app, or similar areas.
Update the title and body of one or more pull requests.
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.
Guide for testing Codex TUI interactively
Choose Rust types for operating system paths across the Codex repository. Use when defining new path-bearing types or explicitly migrating existing ones.
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.
Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.
Testing against remote executors in integration tests.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Guide for testing Codex TUI interactively
Update Codex's pinned `v8` / `rusty_v8` versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update `rusty_v8` artifacts, prepare or validate a V8 release candidate, check `v8-canary`, or diagnose why a V8 version update no longer builds.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.