Skip to content
Back to skills

Github Ci Debug

ASecurity

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.

  • 6,639 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 2, 2026
ai-agentsrailsgit

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add Devin-AXIS/iPolloWork --skill github-ci-debug --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Github Ci Debug?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Github Ci Debug
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/devin-axis-github-ci-debug/badge)](https://www.skillsdirectory.com/skills/devin-axis-github-ci-debug)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: github-ci-debug
description: 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.
disable-model-invocation: false
---

# GitHub CI Debug

Use this skill only for GitHub Actions failures.

## Workflow

1. Resolve the repository and Actions run ID from the supplied URL, PR, or current branch context.
2. Call `actions-failure` through the connected GitHub service.
3. Report the run URL, failing jobs, failing steps, and the most likely root cause supported by the returned evidence.
4. If the check belongs to an external provider, report its URL and do not pretend the GitHub service controls it.
5. Propose the smallest fix tied directly to the failing step.
6. When the user asked for a fix, implement it locally and run the relevant local check.
7. 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.