Run any Skill in Manus with one click

babysit-pr

Stars13

Forks2

UpdatedMarch 31, 2026 at 09:51

Babysit a PR until merge-ready, then ask before merging. Runs pr-merge-prep on a 10-minute loop, monitors readiness (CI, reviews, conflicts), auto-stops when ready, and requires explicit user confirmation to merge. Never merges autonomously. Use when: "babysit this pr", "watch pr until ready", "keep fixing pr until mergeable".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

doodledood

doodledood/claude-code-plugins

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	babysit-pr
description	Babysit a PR until merge-ready, then ask before merging. Runs pr-merge-prep on a 10-minute loop, monitors readiness (CI, reviews, conflicts), auto-stops when ready, and requires explicit user confirmation to merge. Never merges autonomously. Use when: "babysit this pr", "watch pr until ready", "keep fixing pr until mergeable".
user-invocable	true

User request: $ARGUMENTS

Goal

Thin orchestration wrapper: start a recurring pr-merge-prep loop, monitor the PR until it reaches merge-ready state, stop the loop, and ask the user whether to merge. Never merge without explicit user confirmation.

Flow

1. Detect PR

If PR number/URL is in $ARGUMENTS, use it. Otherwise detect from the current branch via gh pr view --json number,url,title,isDraft.

If no PR found, report and stop. If PR is draft, report "PR is draft — nothing to babysit" and stop.

2. Start the Loop

Invoke the loop skill with: "10m /pr-merge-prep $PR_IDENTIFIER"

This starts pr-merge-prep running every 10 minutes in the background.

3. Monitor for Merge Readiness

After starting the loop, immediately run a readiness check (don't wait 10 minutes for the first one). Then continue checking after each loop iteration.

Readiness check — run gh pr view $PR_NUMBER --json mergeable,reviewDecision,statusCheckRollup,reviewRequests,comments and evaluate:

Condition	Ready?
All CI/status checks pass (no pending, no failing)	Required
No unresolved review threads	Required
No merge conflicts (mergeable != CONFLICTING)	Required
Review decision is APPROVED or no reviewers assigned	Required

If all conditions met: PR is merge-ready. Proceed to step 4. If not ready: Log what's still blocking and let the loop continue. The next pr-merge-prep iteration will work on remaining blockers.

4. Stop the Loop

When the PR is merge-ready, stop the cron schedule that was created in step 2. Use CronDelete to remove it.

5. Ask User to Merge

CRITICAL: Never merge automatically. Always ask.

Report the PR status summary to the user:

PR title and URL
All checks passing
Review status
Any remaining open (uncertain) comment threads that pr-merge-prep left for human review

Then ask the user: "PR is ready to merge. Would you like me to merge it?"

If user says yes: merge via gh pr merge $PR_NUMBER --merge (or --squash/--rebase if user specifies)
If user says no or not yet: acknowledge and stop. Do not merge.
If user doesn't respond: do nothing. The PR stays open.

More from this repository

same repository

auto

doodledood/claude-code-plugins

End-to-end autonomous execution: figure-out → define → do, chained without manual approval gates. Use when you want to define and execute without intervention during planning. Triggers: auto, autonomous, end-to-end, just build it, tend pr, babysit pr.

2026-05-1913

define

doodledood/claude-code-plugins

Manifest builder. Turns shared understanding into a verifiable Manifest with Deliverables, Acceptance Criteria, Global Invariants, and Approach. Use when planning features, scoping refactors, debugging complex issues, or whenever a task needs structured thinking before coding. Triggers: define, manifest, scope, plan, spec out, break down.

2026-05-1913

doodledood/claude-code-plugins

Manifest executor. Works through Deliverables verifying every Acceptance Criterion and Global Invariant. Use when executing a manifest, running a plan, implementing a defined task. Triggers: do, execute, run the manifest, implement plan, run plan, execute manifest, ship the manifest.

2026-05-1913

done

doodledood/claude-code-plugins

Completion marker for the /do workflow. Outputs a plain-prose summary of what was built. Called by /do after every Acceptance Criterion and Global Invariant verifies PASS, not directly. Triggers: completion summary, manifest complete, all criteria pass, finish manifest, summarize completion, wrap up, mark done.

2026-05-1913

escalate

doodledood/claude-code-plugins

Structured escalation when /do hits an unrecoverable blocker. Surfaces what was tried, why it failed, and what the user can decide. Called by /do, not directly. Triggers: blocked, can't proceed, unrecoverable failure, need user decision, blocker, hit a wall, escalate, stuck.

2026-05-1913

figure-out

doodledood/claude-code-plugins

Figure things out together — any topic, problem, or idea. Presses relentlessly until shared understanding is reached. Use when you need to understand something before acting, or when figuring it out IS the goal. Triggers: figure out, help me think through, dig deeper, press this, what is really going on, investigate, work through, why does.

2026-05-1913

name	babysit-pr
description	Babysit a PR until merge-ready, then ask before merging. Runs pr-merge-prep on a 10-minute loop, monitors readiness (CI, reviews, conflicts), auto-stops when ready, and requires explicit user confirmation to merge. Never merges autonomously. Use when: "babysit this pr", "watch pr until ready", "keep fixing pr until mergeable".
user-invocable	true

User request: $ARGUMENTS

Goal

Flow

1. Detect PR

If PR number/URL is in $ARGUMENTS, use it. Otherwise detect from the current branch via gh pr view --json number,url,title,isDraft.

If no PR found, report and stop. If PR is draft, report "PR is draft — nothing to babysit" and stop.

2. Start the Loop

Invoke the loop skill with: "10m /pr-merge-prep $PR_IDENTIFIER"

This starts pr-merge-prep running every 10 minutes in the background.

3. Monitor for Merge Readiness

After starting the loop, immediately run a readiness check (don't wait 10 minutes for the first one). Then continue checking after each loop iteration.

Readiness check — run gh pr view $PR_NUMBER --json mergeable,reviewDecision,statusCheckRollup,reviewRequests,comments and evaluate:

Condition	Ready?
All CI/status checks pass (no pending, no failing)	Required
No unresolved review threads	Required
No merge conflicts (mergeable != CONFLICTING)	Required
Review decision is APPROVED or no reviewers assigned	Required

4. Stop the Loop

When the PR is merge-ready, stop the cron schedule that was created in step 2. Use CronDelete to remove it.

5. Ask User to Merge

CRITICAL: Never merge automatically. Always ask.

Report the PR status summary to the user:

PR title and URL
All checks passing
Review status
Any remaining open (uncertain) comment threads that pr-merge-prep left for human review

Then ask the user: "PR is ready to merge. Would you like me to merge it?"

If user says yes: merge via gh pr merge $PR_NUMBER --merge (or --squash/--rebase if user specifies)
If user says no or not yet: acknowledge and stop. Do not merge.
If user doesn't respond: do nothing. The PR stays open.