AutoGineer
Generated banner for Factory Babysit Pr
Generated logo for Factory Babysit Pr

Factory Babysit Pr

Builder.ioOfficialPublished by Builder.io

  • Skill
  • Workflow
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Builder.io

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Factory Babysit PR is a specialized workflow designed to monitor and manage a single, explicitly authorized pull or merge request through its delivery lifecycle. Unlike bulk review tools, this skill focuses on granular control, ensuring that every action—from fixing findings to replying, approving, and merging—is gated by specific, verified conditions. It emphasizes strict adherence to authorization, live state verification, and the preservation of human intent, ensuring that no automated action is taken without meeting all configured requirements.

What it does

  • Verifies authorization and ownership before performing any operations on a PR.
  • Captures a complete live snapshot of the PR state, including checks, reviews, and threads.
  • Dispositions feedback by comparing findings against the diff and source code.
  • Applies fixes only for actionable items within defined scope and risk limits.
  • Enforces separate gates for replying, approving, merging, and soaking.
  • Reports detailed status updates, including blockers and soak progress.

When to use it

  • When you need to manage a specific PR through to completion with high oversight.
  • When you require strict, gated automation for PR interactions like approvals or merges.
  • When you need to ensure that automated fixes are only applied to authorized paths.
  • When you need to monitor a PR's state and ensure it remains stable during a soak period.

Advantages

  • Prevents unauthorized or speculative changes by enforcing strict scope and risk limits.
  • Ensures high reliability by re-verifying the PR state after every mutation.
  • Provides granular control over the delivery lifecycle through independent action gates.
  • Maintains clear audit trails by reporting on all actions taken or withheld.

Usage examples

“Babysit PR #123 in the current repository.”
The agent verifies authorization for PR #123, captures its current state, and begins monitoring for actionable findings or merge readiness based on configured gates.
“Check the status of the PR I am babysitting and apply fixes if ready.”
The agent fetches the latest live snapshot of the PR, evaluates any new findings against the authorized scope, and applies fixes only if all safety and gate conditions are met.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/builderio/factory-babysit-pr/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip factory-babysit-pr.zip -d .agents/skills

Documentation by Builder.io

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

ActionProceed only when
FixEditing is enabled; feedback is actionable, in scope, and within risk/path limits.
PublishPublishing 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.
ReplyReplies are enabled and their conditions hold. Follow configured wording/tone; otherwise do not message.
ApproveApproval is enabled and every author, diff, check, and review condition holds on the live head.
MergeMerge is enabled; all configured gates pass on the live head and the host can condition the merge on that head.
SoakProve 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.

Files

README.md

/factory-babysit-pr

Monitor one explicitly authorized pull or merge request. Each pass checks its live head, review threads, required checks, and mergeability. Fixes, publishing, replies, approvals, merges, and soak requirements each have separate gates.

Use /factory-review-prs for a PR queue and /factory-watchdog for stopped delivery work that needs a verified reminder.

Configure the exact host, repository, PR, authorization, cadence, worktree, and action policies with /factory in .agent-factory/config.yaml. See the Factory configuration reference.

Install

npx @agent-native/skills@latest add

Select Factory to preselect its modules, remove any modules you do not want, then choose the supported client and install scope.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Builder.io
Publisher
Builder.io (Official)
Source
BuilderIO/skills · skills/factory-babysit-pr · commit f4f10b8
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Builder.io.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download factory-babysit-pr.zip