prcheckloop

Automate the repair loop for failing GitHub pull request CI checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually resolving failing GitHub pull request CI checks is repetitive and time-consuming, requiring constant log inspection, code fixes, pushes, and re-monitoring until all checks pass for the latest commit.

Core Features & Use Cases

  • Iterative Check Tracking: Monitors all CI/status checks for the latest PR head SHA, ignoring outdated commit failures to focus on current code issues.
  • Automated Failure Investigation: Parses GitHub Actions and legacy status check logs to classify failures as actionable code issues, flaky tests, or external blockers.
  • Use Case: After pushing review fixes for a feature branch with red CI checks, use this skill to automate the entire repair loop instead of manually handling each failure.

Quick Start

Use the prcheckloop skill to automatically fix all failing checks for the open pull request on your current feature branch.

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 Actions checks on a pull request?

Automating GitHub PR check fixes involves tracking the latest head SHA, parsing failing check logs, applying minimal code fixes, and pushing updates until all checks pass. This skill automates that entire repair loop.

Can I automate code fixes for legacy commit status checks in GitHub?

Yes, automated check resolution can support both GitHub Actions and legacy commit status contexts. The process investigates failing logs, applies actionable code fixes, and pushes updates for both check types.

How do CI check repair loops handle non-actionable failures or external blockers?

Automated PR check repair loops classify failures as actionable code issues, flaky tests, or external blockers. Non-actionable blockers are escalated with precise context rather than attempting an automated fix.

Does automated pull request check resolution work with outdated commit failures?

No, iterative check tracking monitors CI checks specifically for the latest PR head SHA. It ignores outdated commit failures to ensure only current code issues are investigated and resolved.

What is the best way to resolve red CI checks after pushing review fixes?

The best way to resolve red CI checks is to use an automated repair loop that investigates failing logs, applies minimal code fixes for actionable issues, and pushes updates until checks pass.