Classify failed GitHub Actions CI runs into failure categories and write handoff packets.
npx skills add https://github.com/jellyrock/jellyrock --skill ci-triage-jellyrock
Please help me install this Agent Skill. Skill: ci-triage Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/ci-triage Command: npx skills add https://github.com/jellyrock/jellyrock --skill ci-triage-jellyrock
When a GitHub Actions workflow fails on a PR or main branch, developers waste time scrolling through logs to find the root cause. This Skill automates the triage process, classifying failures into known categories and preparing a structured investigation handoff so you can fix issues faster.
Use the ci-triage skill to investigate the failing GitHub Actions run with ID 1234567890 and tell me what went wrong.
High-intent search queries and answers about installing and using this skill.
You can automate CI failure triage by extracting run logs with the gh CLI and analyzing git diffs to classify failures into categories like lint-fail, build-fail, or device-test-fail. This process prepares a structured investigation handoff with file context to speed up root cause identification.
The best way to debug a continuous integration build failure is to automate the extraction of run logs and git diffs to classify the error type. This avoids manual log scrolling and generates a structured handoff packet with the specific failing files for targeted investigation.
Yes, the gh CLI is required to extract GitHub Actions run logs for CI triage. The triage process also uses git for diff analysis to classify failures and assemble the initial file context needed for investigation.
Yes, automated CI triage supports deduplicating GitHub Actions failure analysis. It checks for prior triage on the same run-id and short-circuits if nothing has changed, ensuring that continuous integration failures are only classified once to avoid redundant work.
CI triage handles cross-session resume by writing structured handoff packets with failure logs and file context to the .claude/handoffs/ directory. This allows investigations into CI failures to be paused and resumed across different sessions or after compaction recovery.
Automated CI triage classifies GitHub Actions failures into lint-fail, build-fail, device-test-fail, docs-stale-blocking, and language-coverage-fail categories. This classification helps pinpoint the exact nature of the continuous integration workflow failure for faster resolution.
gioeRetrieves GitHub Actions run data and failure logs via gh CLI, generating structured reports with severity-filtered details.
mvillmowDiagnose CI failures by inspecting logs and reproducing issues locally.
LuminairPrimeIdentify failing GitHub Actions checks and generate a fix plan.
ESO-ToolkitParse GitHub Actions workflow logs to diagnose CI/CD failures.
