pr-monitor

Monitor CI failures, PR age, and stale activity across watched GitHub repositories.

5|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/JansenAnalytics/claudex --skill pr-monitor-jansenanalytics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-monitor
Source: https://github.com/JansenAnalytics/claudex/tree/main/skills/pr-monitor
Command: npx skills add https://github.com/JansenAnalytics/claudex --skill pr-monitor-jansenanalytics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitor GitHub repo health by tracking CI status, PR age, and stale activity, enabling faster remediation.

Core Features & Use Cases

  • Monitor CI status across watched repositories and surface failures quickly.
  • Track PR age and stale activity to highlight bottlenecks and delays in reviews.
  • Configure per-repo watch lists, exclusions, and alert cooldowns to avoid alert fatigue.

Quick Start

Run the monitor script to start real-time checks using the default configuration.

Frequently Asked Questions about pr-monitor

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

FAQPage Schema
How do I monitor GitHub repository health and CI failures across multiple repos?▼

You can track CI failures and PR age across watched repos using local monitor and status scripts configured via a JSON file. This surfaces failures and stale activity quickly for faster remediation.

What's the best way to track stale pull requests and surface review bottlenecks?▼

Monitoring PR age and stale activity highlights review bottlenecks and delays. Local scripts track open pull requests across watched repos to surface issues requiring attention.

Can I configure alert cooldowns and per-repo exclusions for GitHub monitoring?▼

Yes, you can configure per-repo watch lists, exclusions, and alert cooldowns using a config.json file. This governs cadence and thresholds to prevent alert fatigue across watched repositories.

Does this GitHub monitoring approach require external CI pipeline dependencies?▼

No external dependencies are required. The monitoring relies on local scripts, specifically monitor.cjs and status.cjs, alongside a config.json file to govern checks, thresholds, and exclusions independently.

How do I set up a cron job to check CI status and repo health automatically?▼

You can schedule the local monitor script using a cron job to run real-time checks based on your default configuration. This automates CI status monitoring and stale activity tracking at your desired cadence.