pr-monitor

Monitor GitHub pull requests for new commits and resume review workflows.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/cajias/claude-skills --skill pr-monitor-cajias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-monitor
Source: https://github.com/cajias/claude-skills/tree/main/plugins/pr-monitor/skills/pr-monitor
Command: npx skills add https://github.com/cajias/claude-skills --skill pr-monitor-cajias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of manually checking pull requests for new commits, letting you keep reviews current without repeatedly polling GitHub.

Core Features & Use Cases

  • PR discovery and verification: Identify a pull request from a URL, repository and number, or the current git context.
  • Persistent monitoring state: Create and manage a local state file that tracks the repository path, PR number, and last seen commit.
  • Auto-resume workflow: Detect new commits on a monitored PR and resume Claude Code with a notification to review the latest changes.
  • Cleanup and stop control: Remove monitoring state when the PR is merged, closed, or no longer needs attention.

Quick Start

Ask the assistant to monitor a specific GitHub pull request in your repository and keep reviewing it whenever new commits arrive.

Frequently Asked Questions about pr-monitor

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

FAQPage Schema
How do I automatically monitor GitHub pull requests for new commits?

You can automatically monitor GitHub pull requests by using a persistent local state file that tracks the last observed commit SHA, which triggers an auto-resume review workflow whenever new commits are detected on the repository.

Can I auto-resume code review workflows in Claude Code when a PR updates?

Yes, you can auto-resume code reviews in Claude Code. The Skill detects new commits on a monitored GitHub pull request and sends a notification to Claude Code to automatically review the latest changes without manual intervention.

Do I need GitHub CLI authentication to track pull request updates?

Yes, GitHub CLI authentication and repository access are required to track pull request updates. The Skill relies on the GitHub CLI to verify PR status and needs a local state file to persistently monitor the PR number and last seen commit.

How do I stop monitoring a GitHub pull request after it is merged?

You can stop monitoring a GitHub pull request after it is merged or closed by using the cleanup feature to remove the monitoring state file, ensuring the PR no longer requires continuous oversight or automated review follow-up.

What is the best way to identify a pull request for continuous code review monitoring?

The best way to identify a pull request for continuous monitoring is by providing a URL, a repository and PR number, or the current git context. The Skill verifies the PR and registers it in a local state file to track new commits.