Перевод: оболочка страницы на русском; тело навыка (SKILL.md) пока на английском — это исходные инструкции агента.

Pr Babysit

Babysit a PR until CI and comments are clean.

Метаданные навыка

Источник	Встроенный (установлен по умолчанию)
Путь	skills/software-development/pr-babysit
Версия	1.0.0
Автор	VibeOS
Лицензия	MIT
Платформы	linux, macos, windows
Теги	cursor, github, pr, ci, babysit, review
Связанные навыки	github-pr-workflow, github-code-review, requesting-code-review, git-local-workflow

Справка: полный SKILL.md

к сведению

Ниже полное определение навыка, которое VibeOS загружает при активации. Это инструкции, которые видит агент.

PR Babysit

Cursor-style babysit loop: keep a pull request merge-ready by triaging comments, resolving clear conflicts, and fixing in-scope CI until green. Uses terminal + gh/git — no new core tools.

When to Use

• User asks to babysit / land / merge-ready a PR
• CI is red or review comments are blocking
• After opening a PR with github-pr-workflow

Skip when: no GitHub access; user forbids push; work is local-only (git-local-workflow).

Prerequisites

• Inside a git repo with a GitHub remote
• gh authenticated or GITHUB_TOKEN available (see github-pr-workflow)
• Policy: git push / gh pr create|merge are blocked by vibeos-policy unless VIBEOS_POLICY_ALLOW_GITHUB=1 (or equivalent allow) after explicit user approval
• Prefer scripts/run_tests.sh over bare pytest for this monorepo

How to Run

1. Identify the PR (number, URL, or current branch).
2. Snapshot: status, checks, unresolved comments, mergeability.
3. Fix only in-scope failures (this PR’s code). Re-run local tests.
4. Push scoped fixes when policy allows; re-poll CI.
5. Stop when mergeable + green + comments triaged — or report blockers.

# Status snapshot (gh)
gh pr view --json number,title,state,mergeable,statusCheckRollup,url
gh pr checks
gh pr view --comments

# Local verify before push
scripts/run_tests.sh <touched-tests> -q

Quick Reference

Step	Action
Identify	gh pr view / current branch vs base
Conflicts	merge base into branch; abort if intent clashes
Comments	act on valid bugs; explain disagreements briefly
CI	fix code in PR scope; never weaken CI just to pass
Push	only with user approval + policy allow
Done	mergeable, checks green, comments resolved or noted

Procedure

1. Snapshot

• Record PR number, base branch, failing check names, open comment threads.
• Filter out already-resolved review threads when listing comments.

2. Merge conflicts

• Prefer merging/rebasing the base into the feature branch.
• Preserve intent on both sides; if intents conflict, stop and ask.

3. Comments

• Valid bug reports → fix with minimal diff + test when practical.
• Style-only nits → fix if cheap; otherwise note and leave.
• Invalid / out-of-scope → short disagreement, do not drive-by refactor.

4. CI loop

• Reproduce locally with the same test path when possible.
• Push only the files that fix the failure.
• Re-watch checks; if red is unrelated and branch is behind, update from base once, then re-check.
• Never edit workflow files solely to silence a check.

5. Exit

• Report: green / remaining blockers / what was pushed.
• Do not merge unless the user explicitly asked to merge.

Pitfalls

• Do not force-push to main/master.
• Do not expand scope into drive-by cleanups.
• Do not change CI config to “make it green”.
• Without VIBEOS_POLICY_ALLOW_GITHUB=1, stop after local fixes and ask to push.
• Kanban/cron for work that must survive process restart — not this skill alone.

Verification

• gh pr checks all success (or listed remaining failures with owners).
• Unresolved blocking comments addressed or explicitly deferred with reason.
• Local scripts/run_tests.sh green for touched paths.