Analyze GitHub Actions run failures by inspecting job outcomes and step logs.
npx skills add https://github.com/bkircher/skills --skill gh-run-failure
Please help me install this Agent Skill. Skill: gh-run-failure Source: https://github.com/bkircher/skills/tree/main/gh-run-failure Command: npx skills add https://github.com/bkircher/skills --skill gh-run-failure
This Skill helps you quickly diagnose and understand why your GitHub Actions pipelines or jobs are failing, saving you time and frustration during development and deployment.
Use the gh-run-failure skill to analyze the most recent failed GitHub run for the current branch.
High-intent search queries and answers about installing and using this skill.
To debug GitHub Actions pipeline failures, you can analyze run statuses, inspect specific job outcomes, and review detailed step logs to pinpoint the root cause of the error.
Find breaking changes in a failed GitHub Actions run by comparing the commit messages of the failed run against the latest successful run to identify code changes that introduced the failure.
Yes, you need the gh CLI tool installed and authenticated to analyze GitHub CI/CD errors, as the skill relies on it to retrieve run statuses and job logs.
Yes, you can download artifacts from failed GitHub Actions jobs to perform deeper inspection of build outputs and test data during troubleshooting.
The best way to troubleshoot a failing GitHub Actions workflow is to automate the inspection of run statuses and step logs, which helps quickly identify failed jobs and retrieve detailed failure information for remediation.
Strategic-AutomationConfigure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI.
FutureAtomsMonitor and manage GitHub check statuses for pull requests and commits.
MarcoAntoliniCreate Git commits with conventional commit messages.
manastalukdarAnalyze CI/CD pipeline build success rates, flaky tests, and duration trends.
