GitHub CI Debug
SkillProductivityLets your agent diagnose failing GitHub Actions runs and propose a focused fix, editing local code only if asked.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the GitHub CI Debug skill
About this capability
Diagnose failing GitHub Actions runs from bounded run, job, and step evidence, propose a focused fix, and modify the local checkout only when the requested task includes implementation.
What this skill tells your AI
The instructions your AI receives, as published by devin-axis/ipollowork in examples/plugin-packages/github/skills/github-ci-debug/SKILL.md and read by ahel’s review.
Use this skill only for GitHub Actions failures.
Workflow
- Resolve the repository and Actions run ID from the supplied URL, PR, or current branch context.
- Call
actions-failurethrough the connected GitHub service. - Report the run URL, failing jobs, failing steps, and the most likely root cause supported by the returned evidence.
- If the check belongs to an external provider, report its URL and do not pretend the GitHub service controls it.
- Propose the smallest fix tied directly to the failing step.
- When the user asked for a fix, implement it locally and run the relevant local check.
- Summarize remaining uncertainty and what needs a remote rerun.
Guardrails
- Do not rerun or cancel workflows; those actions are not part of this plugin version.
- Do not claim complete log coverage when the service returned only job and step summaries.
- Do not change code when the evidence points to an unrelated infrastructure or flaky failure unless the user chooses that scope.
Signals
- GitHub stars
- 6k
- Forks
- 1k
- Last commit
- Sep 2026
ahel review
S4info
community integration — published by devin-axis, not github
Automated review, not a security audit. Ruleset v1.
Advanced
- Catalog kind
- skill
- Gateway key
github-ci-debug- Source
- github.com/devin-axis/ipollowork