pr-watch

Monitor GitHub pull requests for review feedback and report terminal states.

3|1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill pr-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-watch
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/pr-watch
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill pr-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of monitoring GitHub Pull Requests for review feedback, automatically attempting to fix issues, and reporting on the PR's terminal state, significantly reducing manual oversight.

Core Features & Use Cases

  • Automated Review Monitoring: Continuously polls GitHub PRs for review decisions (Approved, Changes Requested).
  • Auto-Fixing Issues: Integrates with the pr-review-dev skill to automatically address review comments of Critical, Major, and Minor severity, with an option to fix 'Nit' comments.
  • Terminal State Reporting: Exits with a clear status once the PR is Approved, Merged, has been auto-fixed to a terminal state, has timed out, or has reached its maximum fix cycle limit.
  • Use Case: Ensure your critical pull requests are actively managed by automatically fixing review comments and notifying you when the PR is approved or if it gets stuck.

Quick Start

Use the pr-watch skill to monitor pull request number 123 in the org/repo repository.

Frequently Asked Questions about pr-watch

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

FAQPage Schema
How do I automate GitHub PR review monitoring and automatically fix requested changes?

Automated GitHub PR monitoring works by continuously polling pull requests for review decisions and utilizing a sub-skill to automatically address requested changes based on severity. This Skill handles the entire cycle, attempting fixes and reporting the terminal state once approved, merged, or timed out.

Can I use polling to track GitHub pull request feedback in my CI/CD pipeline?

Yes, you can track GitHub pull request feedback in a CI/CD pipeline using polling mechanisms. This Skill integrates with CI/CD pipelines and supports push-based notifications to provide real-time status updates on review feedback and automated fixes.

What is the terminal state when automating GitHub pull request fixes?

The terminal state in GitHub pull request automation is the final status reported after monitoring, indicating the PR was Approved, Merged, auto-fixed, reached a maximum fix cycle limit, or timed out. It provides a clear exit status to reduce manual oversight.

How do I automatically fix Critical and Major review comments on a GitHub pull request?

To automatically fix Critical and Major review comments on a GitHub pull request, this Skill integrates with a sub-skill to address feedback by severity. It automatically attempts to resolve Critical, Major, and Minor issues, with an optional setting to fix Nit comments.

What happens when a monitored GitHub pull request reaches the maximum fix cycle limit?

When a monitored GitHub pull request reaches the maximum fix cycle limit, the automation stops attempting fixes and reports the terminal state. This timeout or cap limit ensures you are notified when a PR gets stuck and requires manual intervention.

Does pr-watch support push-based notifications for real-time PR status updates?

Yes, pr-watch supports push-based notifications for real-time PR status updates. Alongside continuous polling for review decisions, it delivers immediate alerts regarding pull request approvals, merges, or timeouts directly through integrated CI/CD pipelines.