A guided workflow for investigating failed GitHub Actions checks on a pull request. GitHub Actions is GitHub's system for automatically running tests and other tasks.

Use it to inspect failing pull-request checks, summarize the relevant log errors, prepare a fix plan, and implement the fix after approval.

It gathers the failing check details and logs before suggesting a fix, helping separate actionable GitHub failures from checks run by other services.

gh-fix-ci — Skill for Claude Code and Codex by Kevin-Liu-01

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Kevin-Liu-01/Agent-Machines --skill gh-fix-ci

Clone the repo

git clone --depth 1 https://github.com/Kevin-Liu-01/Agent-Machines

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/gh-fix-ci/github.svg)](https://agentmods.dev/skills/kevin-liu-01/agent-machines/gh-fix-ci)

Your own site

<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/gh-fix-ci"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/gh-fix-ci/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/gh-fix-ci"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/gh-fix-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 898 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00072	$0.00898
Opus 5	$0.00036	$0.00449
Sonnet 5	$0.00014	$0.00180
Haiku 4.5	$0.00007	$0.00090

Measured 12d ago against content hash 7b326b4a2f0f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

gh-fix-ci scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to gh-fix-ci — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

knowledge/skills/gh-fix-ci/SKILL.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Read the full file on GitHub · 70 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 70 lines · 72 tokens per session scan A 7b326b4a2f0f

Subscribe to this mod's changes

gh-fix-ci is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (29 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 898 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gh-fix-ci, differing in 0 lines, and is treated as a copy.

CI and CD Claude Code Debugging DevOps and cloud ai-agent cron hermes-agent mcp microvm model-context-protocol

temps-plugin

Build external plugins for the Temps deployment platform. Use when the user wants to create, modify, or debug a Temps plugin binary — a standalone Rust process that communicates with Temps over a Unix domain socket. Also use when the user mentions "temps plugin", "external plugin", "plugin binary", "plugin for temps"…

gotempsh/temps · 120 tokens

ci-debug

Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…

yonatangross/orchestkit · 92 tokens

hunt-cicd

Hunt CI/CD pipeline vulnerabilities — GitHub Actions workflow injection (pullrequesttarget Pwnrequest + ${{ }}-into-shell), self-hosted runner poisoning, OIDC trust-policy abuse, Jenkins script-console RCE and CVE-2024-23897 file read, GitLab CI runner-token registration, Terraform state file leakage, artifact/log…

uphiago/recon-skills · 118 tokens

incident-management

Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.

serac-labs/serac · 42 tokens

observability

Use when you say query agent logs, find slow tool calls, or show agent errors. Query and analyze agent JSONL event logs for debugging, performance analysis, and decision tracing.

rjmurillo/ai-agents · 42 tokens

github-actions-debugger

Debug and monitor GitHub Actions workflow runs. Check run status, view failed job logs, and troubleshoot CI failures. Use this when the user needs to investigate GitHub Actions failures, inspect job output, or identify the root cause of a broken workflow run.

opendatahub-io/ai-helpers · 56 tokens