gh-fix-ci

Files (10)

• LICENSE.txt
• README.md
• SKILL.md
• README.md · agents/
• openai.yaml · agents/
• README.md · assets/
• github-small.svg · assets/
• github.png · assets/
• README.md · scripts/
• inspect-pr-checks.mjs · scripts/

SKILL.md (first lines)

# 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.

* Draft a concise fix plan and request user 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

* `node "skills/gh-fix-ci/scripts/inspect-pr-checks.mjs" --repo "." --pr "<number-or-url>"`
* Add `--json` if you want machine-friendly output for summarization.


## Workflow

1. 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.
2. 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.
3. Inspect failing checks (GitHub Actions only).
   * Preferred: run the bundled script (handles gh field drift and job-log fallbacks):
     * `node "skills/gh-fix-ci/scripts/inspect-pr-checks.mjs" --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>"`
4. 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.
5. Summarize failures for the user.
   * Provide the failing check name, run URL (if any), and a concise log snippet.
   * Call out missing logs explicitly.
6. Create a plan.
   * Draft a concise fix plan and request user approval before implementing.
7. Implement after approval.
   * Apply the approved plan, summarize diffs/tests, and ask about opening a PR.
8. Recheck status.
   * After changes, suggest re-running the relevant tests and `gh pr checks` to confirm.


## Bundled Resources


### scripts/inspect-pr-checks.mjs

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:

* `node "skills/gh-fix-ci/scripts/inspect-pr-checks.mjs" --repo "." --pr "123"`
* `node "skills/gh-fix-ci/scripts/inspect-pr-checks.mjs" --repo "." --pr "https://github.com/org/repo/pull/123" --json`
* `node "skills/gh-fix-ci/scripts/inspect-pr-checks.mjs" --repo "." --max-lines 200 --context 40`

Options:

* `--repo <path>` - path inside the target Git repository (default: `.`).
* `--pr <ref>` - PR number or URL (default: the current branch's PR).
* `--max-lines <n>` - maximum lines in a snippet or tail (default: 160).
* `--context <n>` - lines of context around the failure marker (default: 30).
* `--json` - emit JSON instead of the text report.
* `-h`, `--help` - show the help message and exit.

Exit codes:

* `0` - no failing check was detected.
* `1` - failing checks were analyzed and reported, **or** the inspection could not run.
* `2` - the arguments were invalid.

Because `1` covers both a successful analysis and a failure to run, read the report rather than the exit code to tell the two apart.

From ahandsel/tokyo-hiker, MIT.

More from ahandsel/tokyo-hiker