prcheckloop

Repair GitHub PR checks until all pass or blockers escalate.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly fix GitHub PR check failures by running a repair loop that detects the latest PR head, inspects checks, and iteratively applies fixes until checks are green or a blocker is escalated.

Core Features & Use Cases

  • Detects and inventories GitHub PR checks for the current head SHA.
  • Iteratively fixes actionable issues (code, tests, config), pushes changes, and re-evaluates checks.
  • Escalates blockers with precise context when failures are external or not safely fixable.

Quick Start

Invoke the prcheckloop on a target PR and let it run 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 automatically fix failing GitHub PR checks?

To automatically fix failing GitHub PR checks, you can run an automated repair loop that detects the current PR head SHA, inspects failed check runs, iteratively applies code or config fixes, pushes commits, and re-evaluates until all checks pass or escalate blockers.

What is the process for monitoring GitHub pull request status contexts until completion?

Monitoring GitHub pull request status contexts involves detecting the latest head SHA for a branch or PR number, waiting for all check runs and status contexts to complete or fail, and escalating with precise context if failures are external or not safely fixable.

Do I need GitHub CLI access to automate pull request check repairs?

Yes, automating pull request check repairs requires GitHub CLI access, API permissions to read check runs and status contexts, and the ability to push commits and re-run pushes as needed to iteratively apply fixes.

How to handle GitHub CI checks that fail due to external dependencies?

When GitHub CI checks fail due to external dependencies or unfixable issues, the repair loop escalates these blockers with precise context rather than attempting unsafe fixes, ensuring you are notified of external failures.

Can I target a specific PR number when running an automated check repair loop?

Yes, you can target a specific PR number when running an automated check repair loop, or the process can automatically detect the PR associated with your current branch to begin inspecting and fixing check runs.