ci-pipeline-doctor

What problem does it solve?

CI pipelines can become red or flaky, making it difficult to identify root causes across GitHub Actions, GitLab CI, and similar build systems. This skill analyzes configs, logs, caches, artifacts, and recent changes to surface the highest-signal failure clues and actionable next steps.

Core Features & Use Cases

• Collects high-signal evidence from failing runs, including configuration files, logs, caches, artifacts, and recent commits.
• Narrows down root causes through structured reasoning, evidence-based prioritization, and repeatable triage steps.
• Provides concise, testable action plans with minimal, verifiable steps to reproduce and validate fixes.
• Use case: when a pipeline shows intermittent flakiness or a clear failure, this skill guides triage and repair across CI platforms.

Quick Start

Provide the latest failing pipeline run logs and configuration files, and I will diagnose the root cause and propose a minimal, verifiable fix.