skills.rest
tomzx
tomzxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

handle-pr-ci

Diagnose failing GitHub PR CI checks, apply code fixes, and push changes.

5|Updated Jul 25, 2025
Search Tags:#automation#github#debug#ci#pull-request#code-fix
One-click install
npx skills add https://github.com/tomzx/agents --skill handle-pr-ci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handle-pr-ci
Source: https://github.com/tomzx/agents/tree/main/skills/handle-pr-ci
Command: npx skills add https://github.com/tomzx/agents --skill handle-pr-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically diagnose failing CI checks on GitHub pull requests, identify root causes, apply fixes to the codebase, push changes to the PR branch, and verify that CI passes.

Core Features & Use Cases

  • Fetch PR CI status and identify failing runs.
  • Collect and analyze CI logs to distinguish code failures from flaky tests.
  • Apply fixes, commit, and push changes to the PR branch.
  • Monitor CI until all checks pass and report a green result.
  • Use Case: When a PR fails due to a lint error or test failure, diagnose, fix, and re-run CI to validate the fix.

Quick Start

Run /handle-pr-ci <pr-number> to diagnose failing CI checks, implement fixes, and verify all checks pass.

Frequently Asked Questions about handle-pr-ci

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

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

To fix failing CI checks on a GitHub pull request, this skill fetches the PR status, analyzes CI logs to identify root causes, applies code fixes, pushes changes to the PR branch, and monitors CI until all checks pass.

Can I use the gh CLI to diagnose and resolve lint errors or test failures in CI?▼

Yes, you can diagnose and resolve lint errors or test failures using the gh CLI. This skill requires authenticated gh CLI access to collect CI logs, distinguish code failures from flaky tests, and push fixes directly to the PR branch.

What is the best way to analyze CI logs and distinguish flaky tests from actual code failures?▼

The best way to analyze CI logs and distinguish flaky tests from actual code failures is to fetch the failing CI runs, parse the logs to identify root causes, apply the necessary code fixes, and verify the CI passes with a green result.

Does fixing PR CI failures automatically require write access to the GitHub repository?▼

Yes, fixing PR CI failures requires correct repository scope and the ability to push changes to the PR branch. You need authenticated gh CLI access to apply fixes, commit, push, and monitor the CI checks until they pass.

Why does CI keep failing after I push a code fix to my pull request?▼

If CI keeps failing after you push a code fix, it may be due to unaddressed root causes or flaky tests. This skill collects and analyzes CI logs to identify the true issue, applies the correct fix, and monitors the checks to verify a green result.

Related Skills

Explore More Software Engineering Skills→
LuzzerLuzzer

github

Automate GitHub repository, issue, PR, and CI management via gh CLI.

Community
Intermediate
neonwattyneonwatty
23

pr-creator

Create GitHub pull requests and monitor CI until checks pass.

Community
Advanced
act70255act70255

lint-and-validate

Lint and statically analyze Node.js and Python code with ESLint, Pylint, Ruff, MyPy, and Bandit.

Community
Advanced
majedsiefalnasrmajedsiefalnasr

gh-fix-ci

Diagnose and fix failing GitHub Actions PR checks using gh CLI commands.

Community
Intermediate