pr-monitor

Triage pull request attention events and delegate fixes to a subagent.

3|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/ronaknnathani/relay --skill pr-monitor-ronaknnathani
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-monitor
Source: https://github.com/ronaknnathani/relay/tree/main/skills/pr-monitor
Command: npx skills add https://github.com/ronaknnathani/relay --skill pr-monitor-ronaknnathani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open pull requests accumulate failing checks, review comments, merge conflicts, and stale bases that require constant manual monitoring. This Skill handles one pull request attention event end to end by reading the watcher digest, triaging each item, delegating fixes, and verifying resolution against live GitHub state. ## Core Features & Use Cases - Digest-driven triage: Reads the deterministic watcher digest containing check statuses, review decisions, unresolved threads, and merge state instead of re-fetching broad PR context. - Delegated fixing: Routes real check failures, comments, reviews, threads, and merge conflicts to a single pr-fix subagent call with scoped worklists and answer tokens. - Agent-side actions: Reruns flaky checks, rebases stale branches, re-arms auto-merge, and escalates closed-unmerged pull requests. - Use Case: A CI check fails on your open PR overnight. The watcher wakes this Skill, which classifies the failure as a flake, reruns the check, re-observes the PR to confirm it cleared, and exits. ## Quick Start Ask the agent to run pr-monitor once for your project to triage the current pull request attention items and delegate any fixes.

Frequently Asked Questions about pr-monitor

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

FAQPage Schema
How do I automatically respond to pull request review comments?▼

Run pr-monitor, which reads the watcher digest of unanswered comments and reviews, then delegates replies to a pr-fix subagent. Each reply carries a hidden marker with the item's answers token so the watcher knows exactly which feedback was addressed.

How to handle failing CI checks on a GitHub pull request?▼

The Skill classifies each failing check as an infra flake or real failure by inspecting the run log. Flakes are rerun directly with gh run rerun, while real failures are delegated to the pr-fix subagent with the check names and run ids.

Can pr-monitor run without the watcher running?▼

Yes, invoke it manually and it performs a fresh read-only observation using relay pr watch tick, which records its own digest without changing any watcher schedule. If the tick returns no actionable items, the run stops immediately.

Does pr-monitor merge or approve pull requests?▼

No, it never approves, merges, or dismisses reviews. Auto-merge is only re-armed on approved pull requests based on the default branch, and merging fires solely on genuine human code-owner approval.

Why does the same pull request issue keep waking the watcher?▼

The watcher records no local handled claim, so an item disappears only when the remote GitHub state no longer shows it. If a fix did not actually land, the next observation reports the item again, which is the intended behavior.