monitor-pr

Monitor open pull requests through CI workflows and reviewer comments until merge.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/nexus-a1/claude-skills --skill monitor-pr-nexus-a1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-pr
Source: https://github.com/nexus-a1/claude-skills/tree/main/skills/monitor-pr
Command: npx skills add https://github.com/nexus-a1/claude-skills --skill monitor-pr-nexus-a1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitors an open pull request and shepherds it through CI and review by observing workflows, detecting failures, addressing comments, and looping until a merge decision is reached.

Core Features & Use Cases

  • Automated CI monitoring and failure remediation, looping until green.
  • Comment triage and targeted responses to reviewers, with safe defaults.
  • PR state orchestration across fetch/checkout, tests, and merge decisions via a controlled loop.

Quick Start

Invoke /monitor-pr to start shepherding a PR through CI and review.

Frequently Asked Questions about monitor-pr

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

FAQPage Schema
How do I automate pull request monitoring through CI workflows and reviews?

Automated pull request monitoring shepherds open PRs by observing CI workflows and reviewer comments. It loops through status checks, applies fixes, and replies to reviews until a terminal merge decision is reached.

Can monitoring a PR automatically fix CI failures on my branch?

Yes, monitoring a PR can automatically fix CI failures. It detects failed workflows, applies unambiguous fixes, and loops across branches as needed until CI turns green.

What is the best way to handle reviewer comments on a git pull request automatically?

Handling reviewer comments automatically involves triaging feedback and generating targeted responses. The monitoring loop applies safe defaults, replying to reviews only when the required action is unambiguous.

Do I need the gh CLI to monitor a pull request through CI and review?

Yes, you need the gh CLI to monitor a pull request. The process relies on gh, git, and a git-operator to fetch state, apply mutations, and orchestrate PR state transitions.

What happens when a pull request reaches a terminal state during automated monitoring?

When a pull request reaches a terminal state during monitoring, the process stops looping and produces a structured final report. This report details the CI checks, applied fixes, and merge decision.