Gh Fix CI

1---
2name: "gh-fix-ci"
3description: "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."
4---
5 
6 
7# Gh Pr Checks Plan Fix
8 
9## Overview
10 
11Use 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.
12- If a plan-oriented skill (for example `create-plan`) is available, use it; otherwise draft a concise plan inline and request approval before implementing.
13 
14Prereq: 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).
15 
16## Inputs
17 
18- `repo`: path inside the repo (default `.`)
19- `pr`: PR number or URL (optional; defaults to current branch PR)
20- `gh` authentication for the repo host
21 
22## Quick start
23 
24- `python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"`
25- Add `--json` if you want machine-friendly output for summarization.
26 
27## Workflow
28 
291. Verify gh authentication.
30   - Run `gh auth status` in the repo.
31   - If unauthenticated, ask the user to run `gh auth login` (ensuring repo + workflow scopes) before proceeding.
322. Resolve the PR.
33   - Prefer the current branch PR: `gh pr view --json number,url`.
34   - If the user provides a PR number or URL, use that directly.
353. Inspect failing checks (GitHub Actions only).
36   - Preferred: run the bundled script (handles gh field drift and job-log fallbacks):
37     - `python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"`
38     - Add `--json` for machine-friendly output.
39   - Manual fallback:
40     - `gh pr checks <pr> --json name,state,bucket,link,startedAt,completedAt,workflow`
41       - If a field is rejected, rerun with the available fields reported by `gh`.
42     - For each failing check, extract the run id from `detailsUrl` and run:
43       - `gh run view <run_id> --json name,workflowName,conclusion,status,url,event,headBranch,headSha`
44       - `gh run view <run_id> --log`
45     - If the run log says it is still in progress, fetch job logs directly:
46       - `gh api "/repos/<owner>/<repo>/actions/jobs/<job_id>/logs" > "<path>"`
474. Scope non-GitHub Actions checks.
48   - If `detailsUrl` is not a GitHub Actions run, label it as external and only report the URL.
49   - Do not attempt Buildkite or other providers; keep the workflow lean.
505. Summarize failures for the user.
51   - Provide the failing check name, run URL (if any), and a concise log snippet.
52   - Call out missing logs explicitly.
536. Create a plan.
54   - Use the `create-plan` skill to draft a concise plan and request approval.
557. Implement after approval.
56   - Apply the approved plan, summarize diffs/tests, and ask about opening a PR.
578. Recheck status.
58   - After changes, suggest re-running the relevant tests and `gh pr checks` to confirm.
59 
60## Bundled Resources
61 
62### scripts/inspect_pr_checks.py
63 
64Fetch 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.
65 
66Usage examples:
67- `python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "123"`
68- `python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "https://github.com/org/repo/pull/123" --json`
69- `python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --max-lines 200 --context 40`
70