prcheckloop

Iterate on GitHub PR checks until the latest head SHA is green or a blocker is identified.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill prcheckloop-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prcheckloop
Source: https://github.com/adamtpang/summon.company/tree/main/.agents/skills/prcheckloop
Command: npx skills add https://github.com/adamtpang/summon.company --skill prcheckloop-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After pushing fixes to a GitHub pull request, CI checks often remain red or pending, and manually polling, diagnosing, and re-fixing them is slow and error-prone. This Skill automates that repair loop so a PR reaches a fully green check state or exits with a precise, actionable blocker report. ## Core Features & Use Cases - Latest-head check tracking: Always inspects check runs and status contexts for the current PR head SHA, ignoring stale failures from older commits. - Failure classification and repair: Distinguishes code regressions, lint/type/build mismatches, flakes, external service outages, and permission issues, then fixes actionable failures locally and pushes. - Precise blocker escalation: When a PR cannot go green, it reports the exact failing checks, details URLs, what was tried, and who should unblock it. - Use Case: After addressing review comments on a PR, run this Skill to poll the new CI run, reproduce a failing test locally, push the fix, and confirm all checks pass on the new head SHA. ## Quick Start Ask the agent to keep iterating on the current branch's GitHub PR until all checks on the latest commit are green or it reports exactly what is blocking them.

Frequently Asked Questions about prcheckloop

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

FAQPage Schema
How do I fix failing GitHub PR checks automatically?

Use a repair loop that fetches check runs for the latest head SHA via the gh CLI, classifies each failure, reproduces actionable failures locally, pushes the fix, and re-polls until checks are green or a blocker is identified.

How to check GitHub PR status checks with the gh CLI?

Run gh api on repos/{owner}/{repo}/commits/<sha>/check-runs and /status for the head SHA, or use the GraphQL statusCheckRollup query for a compact PR-level view of check runs and status contexts.

Does this work with GitLab merge requests?

No. This workflow is GitHub-only and relies on the gh CLI and GitHub check-run APIs. For GitLab repositories it stops immediately and directs you to use a GitLab-oriented check-pr flow instead.

Why are my PR checks still failing on old commits?

Checks are attached to specific commit SHAs, so failures from older commits linger on the PR. Always fetch checks for the current headRefOid and ignore results from previous SHAs after each push.

When should a failing CI check be rerun instead of fixed?

Rerun only when evidence suggests a flake or transient infrastructure issue, and only once without code changes. Persistent failures, missing secrets, or branch protection mismatches should be escalated rather than retried.