Curated

Chapter 15 of 44

gh Fix CI

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and…

2 minutes · 354 words · 7 sections

Gh Pr Checks Plan Fix

Overview

Use gh to locate failing PR checks, fetch GitHub Actions logs for actionable failures, summarize the failure snippet, then propose a fix plan and implement after explicit approval.

If a plan-oriented skill (for example create-plan) is available, use it; otherwise draft a concise plan inline and request approval before implementing.

Prereq: authenticate with the standard GitHub CLI once (for example, run gh auth login), then confirm with gh auth status (repo + workflow scopes are typically required).

Inputs

repo: path inside the repo (default .)
pr: PR number or URL (optional; defaults to current branch PR)
gh authentication for the repo host

Quick start

python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"
Add --json if you want machine-friendly output for summarization.

Workflow

Verify gh authentication.
- Run gh auth status in the repo.
- If unauthenticated, ask the user to run gh auth login (ensuring repo + workflow scopes) before proceeding.
Resolve the PR.
- Prefer the current branch PR: gh pr view --json number,url.
- If the user provides a PR number or URL, use that directly.
Inspect failing checks (GitHub Actions only).
- Preferred: run the bundled script (handles gh field drift and job-log fallbacks):
  - python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"
  - Add --json for machine-friendly output.
- Manual fallback:
  - gh pr checks <pr> --json name,state,bucket,link,startedAt,completedAt,workflow
    - If a field is rejected, rerun with the available fields reported by gh.
  - For each failing check, extract the run id from detailsUrl and run:
    - gh run view <run_id> --json name,workflowName,conclusion,status,url,event,headBranch,headSha
    - gh run view <run_id> --log
  - If the run log says it is still in progress, fetch job logs directly:
    - gh api "/repos/<owner>/<repo>/actions/jobs/<job_id>/logs" > "<path>"
Scope non-GitHub Actions checks.
- If detailsUrl is not a GitHub Actions run, label it as external and only report the URL.
- Do not attempt Buildkite or other providers; keep the workflow lean.
Summarize failures for the user.
- Provide the failing check name, run URL (if any), and a concise log snippet.
- Call out missing logs explicitly.
Create a plan.
- Use the create-plan skill to draft a concise plan and request approval.
Implement after approval.
- Apply the approved plan, summarize diffs/tests, and ask about opening a PR.
Recheck status.
- After changes, suggest re-running the relevant tests and gh pr checks to confirm.

Bundled Resources

scripts/inspect_pr_checks.py

Fetch failing PR checks, pull GitHub Actions logs, and extract a failure snippet. Exits non-zero when failures remain so it can be used in automation.

Usage examples:

python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "123"
python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "https://github.com/org/repo/pull/123" --json
python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --max-lines 200 --context 40

Install this repository

$ npx skills add openai/skills

Skills install per repository, not per chapter — the CLI has no documented per-skill form, so we do not print one.

About this skill

Trigger

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/openai/skills, branch main, last pushed 14 July 2026.

Licence

Discovery

44 chapters found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: skills/.curated/*/SKILL.md, skills/.system/*/SKILL.md.

Issue colours

Resolved from a curated brand profile — hue 170°, chroma 0.124. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this chapter so the document has one h1 and no skipped levels:

Shifted “7 headings” from h1 to h2 so the chapter title is the only h1.

Spec compliance

Every chapter satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a chapter come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /openai/skills.md, and each chapter at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Gh Pr Checks Plan Fix

Use gh to locate failing PR checks, fetch GitHub Actions logs for actionable failures, summarize the failure snippet, then propose a fix plan and implement after explicit approval.

If a plan-oriented skill (for example create-plan) is available, use it; otherwise draft a concise plan inline and request approval before implementing.

Prereq: authenticate with the standard GitHub CLI once (for example, run gh auth login), then confirm with gh auth status (repo + workflow scopes are typically required).

repo: path inside the repo (default .)

pr: PR number or URL (optional; defaults to current branch PR)

gh authentication for the repo host

python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"

Add --json if you want machine-friendly output for summarization.

Verify gh authentication.

Run gh auth status in the repo.
If unauthenticated, ask the user to run gh auth login (ensuring repo + workflow scopes) before proceeding.

Resolve the PR.

Prefer the current branch PR: gh pr view --json number,url.
If the user provides a PR number or URL, use that directly.

Inspect failing checks (GitHub Actions only).

Preferred: run the bundled script (handles gh field drift and job-log fallbacks):
- python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"
- Add --json for machine-friendly output.
Manual fallback:
- gh pr checks <pr> --json name,state,bucket,link,startedAt,completedAt,workflow
  - If a field is rejected, rerun with the available fields reported by gh.
- For each failing check, extract the run id from detailsUrl and run:
  - gh run view <run_id> --json name,workflowName,conclusion,status,url,event,headBranch,headSha
  - gh run view <run_id> --log
- If the run log says it is still in progress, fetch job logs directly:
  - gh api "/repos/<owner>/<repo>/actions/jobs/<job_id>/logs" > "<path>"

Scope non-GitHub Actions checks.

If detailsUrl is not a GitHub Actions run, label it as external and only report the URL.
Do not attempt Buildkite or other providers; keep the workflow lean.

Summarize failures for the user.

Provide the failing check name, run URL (if any), and a concise log snippet.
Call out missing logs explicitly.

Create a plan.

Use the create-plan skill to draft a concise plan and request approval.

Implement after approval.

Apply the approved plan, summarize diffs/tests, and ask about opening a PR.

Recheck status.

After changes, suggest re-running the relevant tests and gh pr checks to confirm.

Fetch failing PR checks, pull GitHub Actions logs, and extract a failure snippet. Exits non-zero when failures remain so it can be used in automation.

Usage examples:

python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "123"

python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "https://github.com/org/repo/pull/123" --json

python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --max-lines 200 --context 40

gh Fix CI

Gh Pr Checks Plan Fix

Overview

Inputs

Quick start

Workflow

Bundled Resources

scripts/inspect_pr_checks.py

About this skill

Trigger

Colophon

gh Fix CI

Gh Pr Checks Plan Fix

Overview

Inputs

Quick start

Workflow

Bundled Resources

scripts/inspect_pr_checks.py

Appendix 15.1–15.4

ScriptsPython · 1 file

Assets2 files

Also bundled2 files

About this skill

Trigger

Colophon

Appendix 15.1–15.4

ScriptsPython · 1 file

Assets2 files

Also bundled2 files