pr-monitoring

Monitor a GitHub pull request until merge and required checks pass.

62|2|Updated May 29, 2026
One-click install
npx skills add https://github.com/lucasfcosta/backpressured --skill pr-monitoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-monitoring
Source: https://github.com/lucasfcosta/backpressured/tree/main/skills/pr-monitoring
Command: npx skills add https://github.com/lucasfcosta/backpressured --skill pr-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs often remain open and green without actually landing, which invites premature completion. This Skill ensures continuous monitoring from PR open to merge, guarding against late-breaking issues and blockers.

Core Features & Use Cases

  • Background watch of PR status until merge using GitHub checks and PR state
  • Reads and surfaces blocker conditions to prevent premature completion
  • Works with gh CLI to watch, read logs, and identify merge readiness

Quick Start

Tell the agent which PR to monitor and what counts as done, then let it watch automatically until it lands.

Frequently Asked Questions about pr-monitoring

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

FAQPage Schema
How do I monitor a GitHub pull request until it is merged?

You can monitor a GitHub pull request until merge by running a background watch loop that polls PR status via gh checks and mergeStateStatus. This continuous monitoring ensures the PR lands only after all required CI checks pass and handles blockers and merge readiness.

Why do my GitHub PRs stay green but never actually land?

PRs often remain open and green without actually landing, inviting premature completion. Continuous PR monitoring from open to merge guards against late-breaking issues and blockers, ensuring the PR is truly ready before completion.

Can I use the gh CLI to watch CI status and identify merge readiness?

Yes, you can use the gh CLI to watch CI status, read logs, and identify merge readiness. The monitoring process polls status via gh checks and evaluates mergeStateStatus alongside BEHIND or DIRTY states to determine if a PR is ready to land.

How do I stop premature completion when CI is running on a pull request?

To stop premature completion when CI is running on a pull request, implement a stop-when-merged criterion within a background watch loop. This reads and surfaces blocker conditions, preventing the PR from completing until merge and all required checks pass.

What's the best way to automate pull request monitoring for required CI checks?

The best way to automate pull request monitoring for required CI checks is using a background watch loop that polls status via gh checks and mergeStateStatus. It automatically handles green builds, blockers, and merge readiness until the stop-when-merged criterion is met.