skills.rest
googlarz
googlarzCOMMUNITY
Explore all skills by this author →
GitHub

prcheckloop

Iterate GitHub PR checks to green across PR cycles.

3|Updated Apr 11, 2026
Search Tags:#automation#debugging#github#blockers#ci#pull-request#pr-checks
One-click install
npx skills add https://github.com/googlarz/stapler --skill prcheckloop-googlarz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prcheckloop
Source: https://github.com/googlarz/stapler/tree/main/.agents/skills/prcheckloop
Command: npx skills add https://github.com/googlarz/stapler --skill prcheckloop-googlarz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iteratively keeps GitHub PR checks green by detecting the correct PR, waiting for all checks on the latest head SHA to run, and escalating when failures are external or non-fixable.

Core Features & Use Cases

  • Automatically identify PRs from the current branch or a provided PR number and monitor status checks.
  • Inventory and track all check runs and statuses, including re-checks after fixes.
  • Escalate with precise blockers when issues are external, flaky, or not safely fixable.

Quick Start

Detect the PR from the current branch or a provided PR number and let the agent iterate fixes 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 GitHub PR checks until they pass?▼

Automating GitHub PR checks involves detecting the PR for your current branch, monitoring status checks on the latest head SHA, and iterating fixes until all statuses are green. This process escalates with precise blockers when external or non-fixable failures occur.

What is the best way to monitor and repair failing CI checks on a pull request?▼

Monitoring and repairing CI checks requires inventorying all check runs and statuses on a pull request, pushing fixes directly, and re-checking until green. It escalates unresolved failures by adding blockers when issues are flaky or external.

Do I need the gh CLI to iterate GitHub status checks to green?▼

Yes, iterating GitHub status checks to green requires the gh CLI for access. You also need GitHub authentication and the ability to push fixes or add blockers for unresolved failures to your repository.

Can I automatically detect the PR number from my current branch?▼

Yes, you can automatically detect the PR number from your current branch. The automation process identifies the correct pull request without manual input, or you can provide a specific PR number to monitor and fix its status checks.

How do I handle external or flaky failures when automating PR check repairs?▼

Handling external or flaky failures during PR check repairs involves escalating with precise blockers. When issues are not safely fixable or are external, the automation process stops iterating and raises a blocker to document the unresolved failure.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

merge-pr

Verify and merge GitHub pull requests using the GitHub CLI.

Community
Intermediate
jimmymalhanjimmymalhan
1

Post-Merge Watchdog

Automate post-merge branch cleanup, inventory refreshes, and regression checks.

Community
Advanced
ronniepinnellronniepinnell

iterate-pr

Iterate on pull requests to resolve CI failures and process code reviews.

Community
Advanced
paultyngpaultyng
9

ci-debug-loop

Diagnose failing GitHub Actions runs, apply fixes, and re-trigger CI.

Community
Advanced