prcheckloop

Automate GitHub PR checks to green with iterative fixes and pushes.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/VitorRibeiro45/paperclip --skill prcheckloop-vitorribeiro45
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prcheckloop
Source: https://github.com/VitorRibeiro45/paperclip/tree/main/.agents/skills/prcheckloop
Command: npx skills add https://github.com/VitorRibeiro45/paperclip --skill prcheckloop-vitorribeiro45

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iteratively gets a GitHub pull request's checks green. Detects the PR for the current branch or uses a provided PR number, waits for every check on the latest head SHA to appear and finish, investigates failing checks, fixes actionable code or test issues, pushes, and repeats. Escalates with a precise blocker when failures are external, flaky, or not safely fixable.

Core Features & Use Cases

  • PR detection: automatically identifies the target PR from the current branch or a provided PR number.
  • Check monitoring: tracks all check runs and status contexts on the PR head SHA until they reach a terminal state.
  • Failure remediation: investigates failures, applies minimal code or test changes, and pushes updates to retry.
  • Escalation: raises precise blockers with context when issues are external, flaky, or not safely fixable.
  • Use case: ideal for PRs stuck in CI red after fixes or pending CI to reach green before merge.

Quick Start

Provide the PR number (or run on the current branch) and let the skill loop until all checks are green or a blocker is raised.

Frequently Asked Questions about prcheckloop

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

FAQPage Schema
How do I automate fixing failing GitHub PR checks?

To automate fixing failing GitHub PR checks, this skill detects the target pull request, monitors the latest head SHA for check runs, analyzes failures, pushes code or test fixes, and repeats the loop until all checks are green or a blocker is raised.

What is the best way to monitor pull request CI status until completion?

Monitoring pull request CI status involves tracking all check runs and status contexts on the PR head SHA until they reach a terminal state. This skill automates that wait loop and investigates any resulting failures.

Can I automatically retry a failed pull request check after pushing a fix?

Yes, you can automatically retry failed pull request checks after pushing a fix. The skill applies minimal code or test changes, commits the update to the current branch, and monitors the new head SHA in a capped retry loop.

How does automated PR remediation handle flaky or external CI failures?

Automated PR remediation handles flaky or external CI failures by escalating them as precise blockers. When issues are not safely fixable through code changes, the skill raises context about the failure rather than attempting blind retries.

Do I need a specific PR number to start debugging GitHub CI failures?

You do not need a specific PR number to start debugging GitHub CI failures. The skill can automatically identify the target pull request from your current working branch, or you can provide an explicit PR number to begin the check monitoring loop.