skills.rest
nabitllc
nabitllcOFFICIAL
Explore all skills by this author →
GitHub

prcheckloop

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

Updated Mar 26, 2026
Search Tags:#automation#debugging#pull request#github#gh cli#ci#check runs
One-click install
npx skills add https://github.com/nabitllc/todero --skill prcheckloop-nabitllc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prcheckloop
Source: https://github.com/nabitllc/todero/tree/main/.agents/skills/prcheckloop
Command: npx skills add https://github.com/nabitllc/todero --skill prcheckloop-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A pull request with failing or pending CI checks blocks merging, and manually polling check statuses, reading failure logs, fixing issues, and re-pushing is repetitive and error-prone. This Skill automates that repair loop for GitHub PRs. ## 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 failures, and permission issues, then fixes actionable ones locally and pushes. - Precise blocker escalation: When checks cannot be fixed from the repo, it reports exact failing check names, details URLs, and who should unblock them. - Use Case: After addressing review comments on a PR, CI is still red. Run this Skill to poll the new head SHA, read the failed GitHub Actions logs, fix the failing lint step, push, and confirm all checks turn green. ## Quick Start Check the PR for my current branch, fix any failing CI checks, and keep iterating until all checks on the latest commit are green.

Frequently Asked Questions about prcheckloop

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

FAQPage Schema
How do I fix failing CI checks on a GitHub pull request?▼

Fetch the check runs for the latest head SHA with the gh CLI, read the failed run logs via gh run view --log-failed, classify the failure, apply the smallest fix locally, then push and re-poll until checks pass.

How to check GitHub PR status checks from the command line?▼

Use gh api to query repos/{owner}/{repo}/commits/<sha>/check-runs and the commit status endpoint, or use the GraphQL statusCheckRollup field for a compact PR-level view of all check runs and status contexts.

Does this work with GitLab merge requests?▼

No, this workflow is scoped to GitHub PRs only and relies on the gh CLI and GitHub check-run APIs. For GitLab repositories, it stops and directs you to use the check-pr skill instead.

Why are no checks appearing for my latest commit?▼

Checks can take a moment to register after a push, so poll for up to about two minutes. If none appear, inspect .github/workflows/, workflow path filters, and branch protection rules to find why no workflow was triggered.

When should a failing 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 after one rerun should be investigated or escalated rather than retried in a loop.

Related Skills

Explore More Software Engineering Skills→
spandiosspandios

yeet

Stage, commit, and open a draft GitHub pull request using the GitHub CLI.

Community
Intermediate
sanjanbsanjanb
1

ship

Automates a test, build, review, deploy, and notify pipeline via opencode agents.

Community
Advanced
BluMintIncBluMintInc
2

automated-review-addressing

Automate pull request review feedback by updating the PR head branch.

Official
Advanced
dennisonbertramdennisonbertram
1

github-actions

View GitHub Actions workflow runs, re-run failed jobs, and inspect logs.

Community
Intermediate