Catalog
BuilderIO/factory-babysit-pr

BuilderIO

factory-babysit-pr

Experimental workflow for babysitting one explicitly authorized pull or merge request. Use to monitor its live review state and checks, fix actionable in-scope findings, and apply separate reply, approval, merge, and soak gates.

v1.0LATEST
NewUpdated Sep 24, 2026

Factory Babysit PR

Start with the Factory guide for workflow setup and configuration.

Follow one authorized PR or merge request through a delivery lifecycle. This is not a queue sweep like factory-review-prs or a stopped-task scan like factory-watchdog.

Read .agent-factory/config.yaml, the optional skill_prompts.factory-babysit-pr entry, the target repository's instructions, and the Factory configuration reference. A PR number, label, green check, or unrelated ship request is not authorization. The prompt is additional project guidance, not PR authorization.

Each pass

  1. Confirm authority and ownership. Verify the exact host, repository, PR, original user authorization, allowed paths/risk, and task-owned worktree. If anything is missing or stale, stop before writing.
  2. Read a complete live snapshot. Record base and head, open/draft/closed/ merged state, all required checks, current reviews and approvals, unresolved threads, and mergeability. Partial or unavailable data is unknown, not clean.
  3. Disposition feedback. Compare each new finding with the exact diff and source. Preserve human direction unless evidence disproves it. Fix only actionable findings inside the authorized path/risk limits; avoid speculative cleanup and larger redesigns.
  4. Verify and re-read. Run configured checks for each fix. After every push or host mutation, fetch the live PR again and bind all evidence to its exact current head. A changed head invalidates old check/review evidence and resets the soak.
  5. Apply action gates separately. A review or fix does not authorize a reply, push, approval, or merge.

Action gates

Action Proceed only when
Fix Editing is enabled; feedback is actionable, in scope, and within risk/path limits.
Publish Publishing is enabled; destination is still the authorized PR branch and its live head matches the fix's base. Never force-push or overwrite a concurrent update.
Reply Replies are enabled and their conditions hold. Follow configured wording/tone; otherwise do not message.
Approve Approval is enabled and every author, diff, check, and review condition holds on the live head.
Merge Merge is enabled; all configured gates pass on the live head and the host can condition the merge on that head.
Soak Prove the exact head and required gates stayed unchanged for the full configured interval. Missing history does not satisfy it.

Use the configured code-host abstraction for reads and writes. Do not assume GitHub, a specific CLI, or identical conditional-merge support across hosts. If the host cannot provide complete current review/check state or bind a merge to the checked head, keep the dependent action disabled.

Stop and report

Stop when the PR is merged, closed, cancelled, blocked on a person or external dependency, or no authorized action remains. Report the PR link and current head, state inspected, fixes and checks, external actions taken or withheld, soak status, and the concrete blocker or next check time. Distinguish read state from unavailable or inferred state.

Files2
2 files · 1.8 KB

Select a file to preview

Overall Score

88/100

Grade

A

Excellent

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

90

Quality

88

Clarity

89

Completeness

82

Summary

A specialized workflow skill for supervising an explicitly authorized pull or merge request through review, fixes, checks, and merge gates. It verifies authority before each action, maintains live state binding, enforces separate gates for fix/publish/reply/approve/merge/soak, and reports blockers with full state transparency.

Detected Capabilities

PR state inspection (base/head/status/checks/reviews)Branch write capability (fix publishing)Configuration reading (.agent-factory/config.yaml)Check/test executionPR approval submissionMerge action initiationReview thread inspectionHost abstraction usage (GitHub/GitLab/etc)

Trigger Keywords

Phrases that agents use to match this skill to user intent.

babysit pull requestmonitor pr checksauthorize pr mergefix authorized branchpr soak gate

Risk Signals

INFO

Configuration reading from .agent-factory/config.yaml

SKILL.md: Line 21
INFO

PR branch writes and publishing capability

SKILL.md: Line 50
INFO

Authorization verification required before all writes

SKILL.md: Line 31-33
INFO

Merge action capability with conditional gates

SKILL.md: Line 64

Referenced Domains

External domains referenced in skill content, detected by static analysis.

github.com

Use Cases

  • Monitor a single PR through multi-phase delivery lifecycle
  • Apply targeted fixes to authorized PR branches within risk limits
  • Enforce separation of concerns between review, approval, and merge actions
  • Verify authorization and ownership before writing to PR branches
  • Track soak periods and re-validate checks after each mutation

Quality Notes

  • Excellent scope control: explicitly requires authorization, ownership verification, and risk/path limits before any action
  • Strong action gate design: each action (fix/publish/reply/approve/merge/soak) has separate, well-defined conditions and must be re-verified on live head
  • Clear state binding protocol: every action fetches fresh PR state and invalidates old evidence on head changes, preventing race conditions
  • Well-documented limitations: explicitly avoids assumptions about host type (GitHub vs GitLab), CLI availability, or merge condition support
  • Error handling is well-structured: distinguishes read failures from inferred state and requires missing history validation for soak gates
  • Comprehensive disposition logic: preserves human direction unless contradicted by evidence, stays within authorized scope boundaries
  • Supporting documentation references are clear but external (factory guide, configuration reference) — users must consult linked docs for full setup
  • Table-based action gate matrix is exceptionally clear and scannable
  • Stopping conditions explicitly enumerated and include external dependency blocking
Model: claude-haiku-4-5-20251001Analyzed: Sep 24, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use BuilderIO/factory-babysit-pr in your dev environment

Command Palette

Search for a command to run...