What problem does it solve?
When a pull request's CI pipeline fails, engineers waste time manually digging through job logs to figure out whether each failure is a flaky test, a pre-existing infrastructure issue, or a genuine regression introduced by their changes. This Skill automates that triage by querying Datadog CI Visibility data and producing a structured triage brief with a recommended action per failing job.
Core Features & Use Cases
- Failure Attribution: Runs blame-guard checks against the default branch and other branches to classify each failing job as flaky, infra, regression, or unknown, using
@error_classification fields when available.
- PR Health Reporting: Fetches branch code coverage via
pup code-coverage branch-summary and includes it in a standardized PR Health section alongside quality and security lines.
- Actionable Remediation: Proposes concrete next steps — deep flaky-test investigation via the
dd-triage-flaky-test skill, GitHub Actions rerun via gh run rerun for transient infra failures, or manual log review for unknowns.
- Use Case: A developer pushes a branch and sees three red CI jobs. Instead of reading raw logs, they ask the agent to triage the PR; the Skill reports one regression in their code, one known flaky test, and one pre-existing infra failure, and offers to rerun the transient job.
Quick Start
Ask the agent to investigate why the CI pipeline is failing on your current pull request branch and classify each failure.