pr-check-monitor

Monitors GitHub pull request checks and coordinates CI failure remediation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request checks fail for many reasons — flaky tests, lint errors, build breakage, or even merge conflicts that silently block CI from running — and diagnosing each one manually is slow and error-prone. This Skill watches PR checks, classifies failures, and orchestrates the right fix workflow so the branch reaches a mergeable state. ## Core Features & Use Cases - Conflict-first diagnosis: Detects when GitHub Actions never fired because the PR has base-branch merge conflicts, and guides a rebase plus force-push to unblock CI. - Failure classification and delegation: Categorizes failures (tests, lint, build, security scans, docs, performance) and launches sub-agents with the appropriate skill to fix each one. - Batched, verified fixes: Coordinates fixing all failures on the current head in one pass with a single push, then verifies checks re-run and pass without regressions. - Use Case: After opening a PR, checks are stuck in "Expected" with no CI runs. The Skill detects a CONFLICTING mergeable state, rebases onto the base branch, force-pushes, and then monitors the newly triggered checks through to green. ## Quick Start Ask the agent to monitor the checks on pull request 42 and coordinate fixes for any failures until all checks pass.

Frequently Asked Questions about pr-check-monitor

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

FAQPage Schema
How do I monitor GitHub pull request checks automatically?▼

Use the bundled wait-for-ci-checks script as a single long wait rather than polling or gh run watch loops. It reports the PR head SHA so you can confirm results apply to the commit you launched on, then analyze any failing check logs for root causes.

Why are my GitHub Actions checks not running on a pull request?▼

GitHub Actions does not trigger CI on PRs with merge conflicts against the base branch. Check mergeable and mergeStateStatus with gh pr view; if CONFLICTING or DIRTY, rebase onto the latest base branch and force-push to unblock CI.

How should multiple CI failures on one PR be fixed?▼

Fix every failure on the current head in one pass and push once, rather than pushing per-failure fixes. Classify each failure by type — test, lint, build, security — and delegate each to an appropriate fix workflow with exact file paths and error context.

What should I do when a check keeps failing after fixes?▼

Escalate with detailed analysis when a check fails repeatedly after attempted fixes. For flaky tests, implement or suggest retry mechanisms, and prioritize blocking checks over non-blocking ones when multiple failures occur.

Does this skill fix CI failures directly?▼

No, it acts as an orchestrator rather than fixing issues itself. It analyzes failures, launches sub-agents with the appropriate skills to implement fixes, then verifies the fixes are committed and the checks pass without new regressions.