t1k:babysit-pr

Monitors pull requests and auto-merges them via the GitHub API.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/tranvietanh0/StackTheRing --skill t1k-babysit-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t1k:babysit-pr
Source: https://github.com/tranvietanh0/StackTheRing/tree/main/.claude/skills/t1k-babysit-pr
Command: npx skills add https://github.com/tranvietanh0/StackTheRing --skill t1k-babysit-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-cli, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of monitoring and merging pull requests, handling flaky CI, resolving simple conflicts, and auto-merging when conditions are met.

Core Features & Use Cases

  • Monitor PR State: Continuously checks the status of a pull request.
  • Handle Flaky CI: Automatically retries failing CI runs.
  • Resolve Simple Conflicts: Attempts to resolve simple merge conflicts automatically.
  • Auto-Merge: Automatically merges PRs when conditions are met.
  • Use Case: If you are a developer or a maintainer who wants to automatically handle PRs, this Skill can save you time and reduce manual work.

Quick Start

To monitor a pull request and automatically merge it when ready, use the command: babysit pr <pr-number-or-url>

Frequently Asked Questions about t1k:babysit-pr

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

FAQPage Schema
How do I automatically monitor and merge a pull request on GitHub?

To automatically monitor and merge a pull request, you can use a tool that continuously checks PR status, handles flaky CI tests, resolves simple conflicts, and auto-merges when conditions are met.

Can I automatically retry flaky CI tests on a GitHub pull request?

Yes, you can automatically handle flaky CI tests on a GitHub pull request by using automation that continuously monitors PR status and automatically retries failing CI runs.

How do I auto-resolve simple merge conflicts in a pull request?

To auto-resolve simple merge conflicts in a pull request, you can use an automated PR handling script that attempts to resolve simple conflicts automatically before merging.

Do I need the GitHub CLI to automate pull request merging?

Yes, you need the GitHub CLI and appropriate GitHub API access permissions to automate pull request merging, as the automation requires command-line interaction with GitHub repositories.

What is the best way to handle pull request maintenance for a GitHub repository?

The best way to handle pull request maintenance for a GitHub repository is to use an automated tool that monitors PR states, handles flaky CI, resolves simple conflicts, and merges PRs based on specified conditions.

Why does my automated PR merge fail on merge conflicts?

Automated PR merges fail on merge conflicts because the automation can only resolve simple conflicts automatically; complex conflicts require manual intervention to ensure code integrity before merging.