prcheckloop

Name: prcheckloop
Availability: InStock
Author: navyapdh11

Monitor GitHub PR checks and apply fixes until all pass.

Updated Apr 24, 2026

Search Tags:#automation #github #debug #ci #pull-request #checks

Ready to run

npx skills add https://github.com/navyapdh11/navya-cleaning-april --skill prcheckloop-navyapdh11

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prcheckloop
Source: https://github.com/navyapdh11/navya-cleaning-april/tree/main/.agents/skills/prcheckloop
Command: npx skills add https://github.com/navyapdh11/navya-cleaning-april --skill prcheckloop-navyapdh11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iteratively brings a GitHub pull request to a fully green check state by continuously monitoring the checks on the latest PR head SHA. It detects the PR for the current branch or uses a provided PR number, waits for every check to appear and finish, and then investigates failing checks, fixes actionable code or test issues, pushes updates, and repeats.

Core Features & Use Cases

Monitor and synchronize GitHub PR checks against the latest head SHA.
Automatically fix actionable code or test issues and push updates to the PR.
Escalate precise blockers when failures are external, flaky, or not safely fixable.

Quick Start

Invoke the skill on a GitHub repository and optionally specify a PR number; it will monitor the latest PR head SHA, detect failing checks, apply fixes, push changes, and repeat until all checks are green or a blocker is escalated.

Frequently Asked Questions about prcheckloop

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

FAQPage Schema

How do I automatically fix failing GitHub pull request checks?▼

To automatically fix failing GitHub PR checks, you need a tool that monitors the latest PR head SHA, detects failing check runs via GitHub APIs, applies actionable code or test fixes, and pushes updates. This loop repeats until all checks reach a terminal green state.

What is the best way to monitor GitHub PR checks against the latest head SHA?▼

Monitoring GitHub PR checks against the latest head SHA involves querying check-runs and status contexts through GitHub APIs. The process waits for every check to finish, investigates failures, and branches on a configurable max-iteration loop to apply fixes and push updates.

How do I debug CI failures that happen after a pull request review?▼

Debugging CI failures after a PR review requires detecting the relevant PR from your current branch, waiting for checks to finish, and investigating the failing check runs. Actionable code or test issues are fixed and pushed, while external or unsafe issues are escalated as precise blockers.

Can I automate pushing code fixes to a GitHub PR until checks turn green?▼

Yes, you can automate pushing fixes to a GitHub PR by iteratively monitoring check runs on the latest head SHA. The process applies fixes to actionable failures, pushes updates, and repeats this loop until all checks pass or a blocker is escalated.

What happens when a GitHub PR check fails due to an external issue?▼

When a GitHub PR check fails due to an external issue, the automation escalates precise blockers. It recognizes when failures are external, flaky, or not safely fixable, records the blocker details, and stops the iteration loop instead of attempting a fix.

Do I need a PR number to start automating GitHub check runs?▼

No, you do not need a PR number to start. The automation can automatically detect the relevant PR from your current branch, or you can optionally specify a PR number to target a specific pull request for monitoring and fixing check runs.