ci-debug

Diagnose CI failures by analyzing logs, tests, and runs to pinpoint root causes.

1|1|Updated Mar 6, 2026

Search Tags:#debugging #logs #github-actions #diagnose #ci #flaky-tests

Ready to run

npx skills add https://github.com/dennisonbertram/go-agent-harness --skill ci-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-debug
Source: https://github.com/dennisonbertram/go-agent-harness/tree/main/skills/ci-debug
Command: npx skills add https://github.com/dennisonbertram/go-agent-harness --skill ci-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose CI failures by parsing logs, identifying flaky tests, comparing with passing runs, and suggesting fixes.

Core Features & Use Cases

Systematic log analysis across CI runs to identify failure patterns
Flaky-test detection by comparing failing and passing runs
Actionable remediation guidance and step-by-step debugging workflows

Quick Start

Use the ci-debug skill to diagnose a failing CI run by collecting logs, identifying failure patterns, and proposing fixes.

Frequently Asked Questions about ci-debug

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

FAQPage Schema

How do I diagnose flaky tests in GitHub Actions CI pipelines?▼

To diagnose flaky tests in GitHub Actions, this Skill compares failing and passing CI runs to detect inconsistent test patterns and pinpoint root causes. It analyzes accessible logs and CI artifacts to identify intermittent failures.

What is the best way to systematically analyze CI logs for failure patterns?▼

Systematically analyzing CI logs involves parsing standard pipeline artifacts to detect failure patterns across runs. This Skill identifies regressions by comparing failed versus passing runs and proposing concrete remediation steps.

Can I use this to debug CI failures outside of GitHub Actions?▼

Yes, you can diagnose CI failures outside of GitHub Actions if your pipeline provides accessible logs and artifact data. The Skill applies to any CI system where you can collect logs and compare passing and failing runs.

How do I find the root cause of a regression in my CI pipeline?▼

Finding the root cause of a CI regression requires comparing failed runs against known passing runs to isolate changes. This Skill parses CI logs and test artifacts to pinpoint the exact failure point and suggest actionable fixes.

Does diagnosing CI failures require any specific testing frameworks?▼

Diagnosing CI failures does not require specific testing frameworks as long as your pipeline generates standard CI logs and artifact data. The Skill parses these accessible outputs to detect failures and propose remediation steps.