monitor-pr

Monitor GitHub Pull Request CI status, apply automated fixes, and merge when checks pass.

Updated Mar 5, 2026

Search Tags:#automation #git #workflow #ci/cd #monitoring #pull request #github actions

Ready to run

npx skills add https://github.com/matthiaskloft/claude-skills --skill monitor-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: monitor-pr
Source: https://github.com/matthiaskloft/claude-skills/tree/main/workflow-automation/skills/monitor-pr
Command: npx skills add https://github.com/matthiaskloft/claude-skills --skill monitor-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the tedious process of monitoring a Pull Request's CI status, handling minor failures, and merging it once all checks pass, freeing up developers from constant oversight.

Core Features & Use Cases

Background CI Monitoring: Continuously checks CI status every 4 minutes.
Automated Fixes: Attempts to fix common CI failures and address simple review comments.
Auto-Merge: Merges the PR once all checks pass and reviews are approved.
State Tracking: Resumes monitoring across sessions using .workflow-state.json.
Use Case: After shipping a feature, you can ask Claude to "monitor this PR" and it will handle the CI checks, fixes, and merging without further intervention, even if you go offline.

Quick Start

Use the monitor-pr skill to start watching the current pull request's CI status and auto-merge it when ready.

Frequently Asked Questions about monitor-pr

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

FAQPage Schema

How do I automate GitHub pull request monitoring and auto-merge after CI passes?▼

To automate pull request monitoring, the Skill continuously checks CI status every 4 minutes, attempts automated fixes for simple failures or review comments, and merges the PR once all checks pass and reviews are approved.

Can I resume monitoring a GitHub Actions workflow across sessions if I go offline?▼

Yes, you can resume monitoring a GitHub Actions workflow across sessions. The Skill persists its tracking state locally using a `.workflow-state.json` file, allowing the automated CI monitoring and merging process to resume seamlessly.

How does automated PR fixing work for failing CI checks and review comments?▼

Automated PR fixing works by detecting failing CI checks and simple review comments, then attempting automated fixes directly on the branch. It iterates through these fixes while continuously monitoring the status every 4 minutes before merging.

What are the limitations of automating GitHub PR merges with branch safety checks?▼

Limitations of automating PR merges include pre-flight checks that validate branch name safety and prevent duplicate monitors from running. It also relies on automated fixes for simple failures, meaning complex CI errors or deep review threads may require manual intervention.

Do I need GitHub Actions to use automated pull request monitoring and merging?▼

You do not need explicit GitHub Actions configurations to use this monitoring. The Skill operates by checking the CI status of your existing GitHub Pull Request workflow and handling the merging process independently through its own background monitoring loop.

What is the best way to handle pull request state persistence for cross-session CI monitoring?▼

The best way to handle pull request state persistence for cross-session CI monitoring is using a local `.workflow-state.json` file. This approach stores the monitoring context, allowing the automated checks and merge attempts to resume after interruptions.