skills.rest
jonmumm
jonmummCOMMUNITY
Explore all skills by this author →
GitHub

babysit-pr

Monitor PR CI checks and surface failures for diagnosis and fixes.

2|Updated Feb 23, 2026
Search Tags:#automation#merge#ci#pull-request#monitor#qr-code
One-click install
npx skills add https://github.com/jonmumm/skills --skill babysit-pr-jonmumm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: babysit-pr
Source: https://github.com/jonmumm/skills/tree/main/babysit-pr
Command: npx skills add https://github.com/jonmumm/skills --skill babysit-pr-jonmumm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, eas, jq, and includes scripts (resource) components.

What problem does it solve?

Monitor PR CI to ensure changes don't break builds, automate diagnosis, fix what can be fixed, publish mobile previews via QR codes, and merge when green.

Core Features & Use Cases

  • Continuous PR monitoring and CI status checks
  • Automated remediation guidance and fixes for common failures
  • Preview distribution via QR codes for mobile testing
  • Auto-merge workflow when checks pass and approvals exist

Quick Start

Start monitoring a PR by running the monitor script with the PR number, then the agent will diagnose failures, fix issues, post a QR code for previews, and auto-merge when all checks pass.

Frequently Asked Questions about babysit-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request CI monitoring and auto-merge?▼

Automate pull request CI monitoring by running the monitor script with a PR number to continuously watch checks, diagnose failures, attempt automated fixes, and auto-merge when all checks pass.

Can I automatically fix failing CI checks on a pull request?▼

Yes, you can fix failing CI checks through automated remediation guidance, which diagnoses common failures and applies fixes before re-evaluating the pull request status.

How do QR codes work for mobile pull request previews?▼

QR codes for mobile previews are generated and posted directly to the pull request, allowing testers to scan and access the deployment build after CI checks are evaluated.

Do I need GitHub CLI and EAS to monitor pull request checks?▼

Yes, you need GitHub CLI (gh) and EAS installed, along with jq, to monitor pull request checks, process CI statuses, publish mobile previews, and execute merges.

What is the best way to merge a pull request only after CI passes?▼

The best way to merge a pull request after CI passes is using an auto-merge workflow that continuously watches checks and completes the merge once approvals exist and all statuses are green.

Why does my pull request auto-merge not trigger after CI passes?▼

Auto-merge does not trigger if required approvals are missing or if the continuous monitoring script detects unresolved CI failures that cannot be automatically remediated.

Related Skills

Explore More Software Engineering Skills→
devs6186devs6186

github-workflow-automation

Automates GitHub workflow management with GitHub Actions and gh CLI for CI, PR, and release tasks.

Community
Intermediate
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
amo-tech-aiamo-tech-ai

cicd-pipeline

Automate GitHub Actions CI/CD pipelines for build, test, lint, and deployment workflows.

Community
Intermediate
vm0-aivm0-ai
1.1k

pull-request

Automate GitHub pull-request creation, merging with CI validation, and comments.

Official
Intermediate