Monitor one explicitly authorized pull or merge request, inspect current reviews and checks, and fix actionable findings within scope. Apply separate permission and verification conditions before publishing fixes, replying, approving, or merging.
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.
Review the instructions the agent will receive before you install.
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.
| 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 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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Guide public skill additions and updates through file placement, catalog documentation, installation discovery, integration settings, and validation. Distinguish ordinary skills from instruction-based, app-backed, and generated skills so each receives the appropriate checks.
Monitor another AI agent’s work and independently investigate the same task. Compare the original request with actual changes and test evidence, report gaps and concrete follow-up steps, and make limited fixes when authorized.
Open Agent-Native apps beside the conversation through Dispatch MCP, a connection for app tools. Create or edit content using the current screen and selection, then read saved results back to confirm the changes.
Organize large coding tasks with Claude Fable directing lower-cost subagents. Delegate bounded research, edits, and tests, then have Fable verify evidence, resolve conflicting findings, integrate changes, and review the final result.
Organize work so an expensive AI model handles planning, judgment, and final review while cheaper helper agents perform bounded research, coding, and testing. Define ownership and verification requirements, then inspect the evidence and integrate their results centrally.
Configure a software delivery workflow that turns selected feedback and maintenance signals into verified, reviewed changes. Define information sources, schedules, working directories, and separate permissions for actions such as implementation, merging, deployment, and notifications.