ci-debug-loop

Diagnose failing GitHub Actions runs, apply fixes, and re-trigger CI.

9|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/paultyng/skill-issue --skill ci-debug-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-debug-loop
Source: https://github.com/paultyng/skill-issue/tree/main/skills/ci-debug-loop
Command: npx skills add https://github.com/paultyng/skill-issue --skill ci-debug-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually debugging failing CI runs is time-consuming, requiring repeated log checks, fix attempts, and run re-triggers that disrupt development workflows.

Core Features & Use Cases

  • Automated CI Monitoring: Watches GitHub Actions runs for the current branch and tracks their status in real time.
  • Intelligent Log Diagnosis: Uses a two-stage subagent pipeline to parse large CI logs, identify root causes, and pinpoint failing files or lines.
  • Iterative Fix & Re-run: Applies mechanical fixes automatically, re-triggers CI runs, and repeats until the build passes or escalation is needed.
  • Use Case: When a PR's CI fails with an unclear error, use this skill to automatically pull logs, find the root cause, apply a fix, and re-run the workflow without manual intervention.

Quick Start

Use the ci-debug-loop skill to resolve the failing CI run on your current branch.

Frequently Asked Questions about ci-debug-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically fix failing GitHub Actions CI runs?

Automated CI fixing uses a subagent pipeline to parse GitHub Actions logs, diagnose root causes, apply mechanical fixes, and re-trigger runs iteratively until the build passes. This resolves continuous integration failures without manual log checks.

What is the best way to debug continuous integration failures from unclear errors?

Continuous integration debugging is best handled by intelligent log diagnosis, which parses large CI logs to pinpoint failing files or lines and identify root causes automatically. This eliminates the need for manual log sifting.

Can I use an automated workflow to monitor GitHub Actions status on my current branch?

Yes, automated CI monitoring watches GitHub Actions runs for your current branch and tracks their status in real time. This monitors pull request workflows and detects failures immediately as they happen.

Does iterative CI log analysis work for large GitHub Actions log files?

Iterative CI log analysis handles large GitHub Actions log files by using a two-stage subagent pipeline to parse them, extract root causes, and pinpoint failing lines. It processes extensive logs without manual intervention.

What happens when automated CI fixing cannot resolve a build failure?

When automated CI fixing cannot resolve a build failure, the workflow escalates the unresolvable errors or infrastructure-related outages. This ensures persistent CI failures are flagged for manual intervention.