Identify root causes of failing GitHub Actions runs for a PR or branch.
npx skills add https://github.com/fall-out-bug/sdp_lab --skill ci-triage-fall-out-bug
Please help me install this Agent Skill. Skill: ci-triage Source: https://github.com/fall-out-bug/sdp_lab/tree/main/.agents/skills/ci-triage Command: npx skills add https://github.com/fall-out-bug/sdp_lab --skill ci-triage-fall-out-bug
Investigate failing GitHub Actions runs and produce root-cause plus Beads follow-up.
Supply a PR number or branch name and ask the AI to generate a CI triage report with root-cause and a Beads follow-up.
High-intent search queries and answers about installing and using this skill.
To identify the root cause of failing GitHub Actions runs, supply a PR number or branch name to collect CI signals, classify the failure, and generate a triage report with proposed minimal fixes.
CI triage works by gathering signals from PR checks and GitHub Actions runs to determine status, classifying root causes, and proposing actionable fixes for your branch.
Yes, you can automatically create a Beads follow-up item for failing CI workflows by linking the root-cause analysis directly to the feature deck for traceability.
The best way to propose minimal fixes for failing CI jobs is to apply automated triage workflows that classify root causes and generate actionable recommendations based on gathered evidence.
No, you can supply either a PR number or a branch name to gather CI signals and generate a root-cause report.
TMYTiMidlYInspect failing GitHub Actions PR checks and summarize actionable log snippets.
KubeHealDiagnose and fix GitHub Actions failures, PR conflicts, and Dependabot PRs via GitHub CLI.
cpfcoachingManage tasks, dependencies, and follow-ups in Beads workspaces via bd CLI.
NagyViktInspect GitHub Actions PR checks and logs to diagnose CI failures.
