tend-pr

Automate GitHub PR tending with rebases, CI fixes, and timeout handoffs.

3|1|Updated Jun 20, 2016
One-click install
npx skills add https://github.com/paulchiu/dotfiles --skill tend-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tend-pr
Source: https://github.com/paulchiu/dotfiles/tree/main/.config/opencode/skills/tend-pr
Command: npx skills add https://github.com/paulchiu/dotfiles --skill tend-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates ongoing tending of a pull request to keep it merge-ready, ensuring CI stays green and the PR lands or is handed off at timeout.

Core Features & Use Cases

  • Self-starting loop that monitors a single PR for merge status, CI results, and base-branch alignment.
  • Rebase and fix CI failures automatically, push fixes, and return control to user when timeout or merge occurs.
  • Collision handling: detects overlapping loops and prompts user for cancel/keep/run-both before proceeding.

Quick Start

Provide the PR identifier, loop interval, timeout, and collision handling preferences, then start the loop.

Frequently Asked Questions about tend-pr

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

FAQPage Schema
How do I automate pull request monitoring to keep CI green until merge?

Automated pull request monitoring uses a self-starting loop to continuously check PR state, CI status, and base-branch alignment, applying rebases and automated fixes until the PR merges or times out.

What is the best way to automatically rebase a GitHub PR when the base branch updates?

Automatically rebasing a GitHub PR when the base branch updates is handled by a monitoring loop that detects rebase needs and pushes the updated branch, ensuring the PR remains merge-ready without manual intervention.

Can I automatically fix CI failures on a pull request without manual intervention?

Yes, you can automatically fix CI failures by configuring a tending loop that detects failing checks, applies automated fixes, and pushes the updates to the pull request branch.

How does collision handling work when multiple automated PR tending loops run simultaneously?

Collision handling for simultaneous PR tending loops detects overlapping processes and prompts the user to choose between canceling, keeping one, or running both before proceeding with the automation.

What happens when an automated pull request monitoring loop times out before merge?

When a pull request monitoring loop times out before merge, the automation stops and returns control to the user, ensuring handoff occurs rather than leaving the loop running indefinitely.

What inputs do I need to start automating ongoing tending of a pull request?

To start automating ongoing PR tending, you need to provide the PR identifier, loop interval, timeout duration, and collision handling preferences before the monitoring loop begins.