pr-watcher

Name: pr-watcher
Availability: InStock
Author: blackplume233

Monitor GitHub open PRs and dispatch them to the pr-handler workflow.

12|1|Updated Feb 19, 2026

Search Tags:#automation #workflow #github #pull-requests #pr-watcher

Ready to run

npx skills add https://github.com/blackplume233/Actant --skill pr-watcher

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-watcher
Source: https://github.com/blackplume233/Actant/tree/main/.agents/skills/pr-watcher
Command: npx skills add https://github.com/blackplume233/Actant --skill pr-watcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub pull requests require constant monitoring and orchestration to trigger automated workflows. This skill acts as a long-running watcher that polls Open PRs and delegates per-PR processing to the pr-handler.

Core Features & Use Cases

Continuous PR discovery and orchestration of the pr-handler five-stage flow.
Idle-aware exit after a configurable number of idle rounds to conserve resources.
Safe state tracking of processed and failed PRs, with reprocessing on new pushes.

Quick Start

Start the PR watcher with default settings to poll for open PRs and dispatch them to pr-handler for processing.

Frequently Asked Questions about pr-watcher

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

FAQPage Schema

How do I automate continuous GitHub pull request monitoring?▼

This skill automates continuous GitHub pull request monitoring by using a loop-based polling model to discover open PRs and delegate per-PR validation to the pr-handler workflow for sequential batch processing.

How does the watcher handle multiple open PRs in batches?▼

The watcher handles multiple open PRs by orchestrating the pr-handler five-stage flow to process them in sequence. It safely tracks processed and failed PRs to ensure each pull request is validated individually.

Can I automatically reprocess GitHub pull requests when new pushes occur?▼

Yes, you can automatically reprocess GitHub pull requests when new pushes occur. The watcher maintains safe state tracking of processed and failed PRs to trigger reprocessing upon detecting new code changes.

Does the PR watcher stop automatically when there are no open pull requests?▼

The PR watcher stops automatically when there are no open pull requests by using an idle-aware exit mechanism. It conserves resources by exiting after a configurable number of idle polling rounds.

Do I need the pr-handler workflow to use this PR watcher?▼

Yes, you need the pr-handler workflow because this watcher acts as an orchestrator. It continuously polls for open PRs and relies entirely on the pr-handler to execute the actual per-PR validation and merge operations.