prcheckloop

Automate GitHub pull request checks to green with fixes and escalation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iteratively drives a GitHub PR to a fully green check state by detecting the target PR (from the current branch or a provided PR number), waiting for all checks on the latest head SHA to appear and finish, investigating failures, applying actionable code or test fixes, pushing changes, and repeating until green. Escalates precisely when failures are external, flaky, or not safely fixable, and complements broader PR workflows.

Core Features & Use Cases

  • Detect and track the PR from the current branch or explicit PR number.
  • Monitor both check runs and status contexts for the latest PR head SHA.
  • Automatically fix actionable failures, commit, and push to retry.
  • Escalate with precise blockers for external or flaky issues and guide next steps.
  • Real-world use: keep PRs moving in CI-heavy projects by reducing manual triage.

Quick Start

Start the prcheckloop skill on your repository to monitor the current branch's PR and automatically push fixes until all checks are green.

Frequently Asked Questions about prcheckloop

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

FAQPage Schema
How do I automate GitHub PR checks until all statuses are green?

Automating GitHub PR checks involves looping through check runs and status contexts on the latest head SHA, analyzing failures, pushing code fixes, and repeating until all checks pass or a blocker is escalated.

Can I automatically fix failing CI checks on a pull request?

Yes, you can automatically fix failing CI checks by investigating actionable failures, applying code or test fixes, committing, and pushing changes to the PR branch to trigger a retry.

What happens when a GitHub PR check fails due to external or flaky issues?

When a GitHub PR check fails due to external or flaky issues, the automation escalates with precise blockers and guides next steps rather than attempting unsafe fixes.

How do I monitor both check runs and status contexts for a pull request?

Monitoring both check runs and status contexts requires tracking the latest PR head SHA, waiting for all checks to appear and finish, and evaluating the combined results for failures.

Does this PR check loop work with a specific pull request number instead of the current branch?

Yes, the PR check loop works with a specific pull request number by allowing you to provide the PR number explicitly, or it can automatically detect the PR from the current branch.

When should I not use automated PR check fixing?

You should not use automated PR check fixing when failures are external, flaky, or not safely fixable, as the automation will escalate these blockers instead of attempting unsafe modifications.