Github ci failure triage

Skill yeaight7/agent-powerups/plugins/github-ops/skills/github-ci-failure-triage

Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more

Install

npx -y skills add yeaight7/agent-powerups --skill github-ci-failure-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a GitHub PR shows failing checks and a clean failure readout is needed before changing any code.

SKILL.md

3.2 KB, 728 tokens by cl100k_base, as published. Nobody here has run it

Purpose

Produce a clean, GitHub-native readout of failing PR checks before any code is edited. Triage first: summarize the breakage and propose a local fix plan; implement only after approval when the task is framed as triage-first.

When to Use

A PR is red and the cause is unknown
The user asks why CI is failing before asking for a fix
A triage-first readout must precede any code edits

Inputs

The PR number or URL (or the current branch to resolve it from)
gh CLI authenticated for the repository, or a GitHub connector

Core Rules

Resolve the PR first
Inspect failing checks before guessing
Prefer GitHub-native data (gh or a GitHub connector) over screenshots or copied snippets
Summarize the failure before proposing code changes
Implement only after approval when the task is framed as triage-first
Do not auto-commit, auto-push, or auto-rerun remote writes without approval

Workflow

Resolve the PR:

gh pr view <number-or-url> --json number,title,headRefName,url
gh pr view --json number,title,headRefName,url    # from the current branch

Inspect failing checks. List checks, isolate failing GitHub Actions jobs, and pull only the failing logs:
```
gh pr checks <number>
gh run list --branch <head-branch> --limit 10
gh run view <run-id> --json jobs        # job-level status
gh run view <run-id> --log-failed       # logs from failing steps only
```
If a check is external (not GitHub Actions), report its URL and keep it out of local log parsing.
Summarize the failure:
- failing job
- likely root cause
- relevant log snippet
- affected files or subsystem
Propose the fix plan:
- what to change locally
- what to validate locally first
- what remains remote-only
Implement only when the user wants the fix. Keep changes traceable to the failing signal; rerun the narrowest meaningful local validation first.

Bundled Helper

scripts/inspect_pr_checks.py — use it when you want a structured check summary instead of raw gh output.

Output

Failing job(s) with a root-cause hypothesis and the minimal relevant log snippet
Affected files or subsystem
A local fix plan with validation steps, separated from remote-only actions

Verification

PR resolved explicitly (number/URL or current branch)
Failure evidence pulled from GitHub-native data, not screenshots or pasted snippets
Log excerpt limited to the failing step, not the whole run log
Summary written before any code change was proposed
No remote writes (commit/push/rerun) performed without approval

Failure Modes

Guess-first triage — proposing fixes before reading the failing job's log.
Log dumping — pasting entire run logs instead of --log-failed output for the failing step.
Unapproved remote writes — rerunning workflows or pushing while the task was triage-first.
Parsing external checks locally — non-Actions checks only expose a URL; report it instead.