dd-unblock-pr

Classifies failing PR CI jobs as flaky, infra, or regression and proposes targeted remediation actions.

1.0k|115|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/datadog-labs/pup --skill dd-unblock-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dd-unblock-pr
Source: https://github.com/datadog-labs/pup/tree/main/skills/dd-unblock-pr
Command: npx skills add https://github.com/datadog-labs/pup --skill dd-unblock-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about dd-unblock-pr

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

FAQPage Schema
How do I find out why my PR CI pipeline is failing?

Run this Skill against your PR branch; it queries Datadog CI Visibility for failing jobs and tests, then classifies each failure as flaky, infra, or regression using blame-guard checks against the default branch and other branches. You receive a triage brief with evidence and a recommended action per job.

How to tell if a CI test failure is flaky or a real regression?

The Skill checks Datadog's flaky tests list for an active flaky state, then compares failure counts on the default branch and across other branches. A failure absent from the default branch and other branches is classified as a regression introduced by the PR.

Does this Skill work with CI providers other than GitHub Actions?

Yes, failure classification works with any CI provider reporting to Datadog CI Visibility. However, the automated retry action via `gh run rerun` only applies to GitHub Actions; for other providers it shares the pipeline URL for manual retry.

What prerequisites are needed to triage a failing PR with Datadog?

You need the pup CLI installed and authenticated to Datadog, plus the dd-pup skill. For deep flaky-test investigation, the dd-triage-flaky-test skill is required, and the repository must send CI Visibility data to Datadog.

Why does the PR Health section show 'No data available' for quality and security?

Code quality and security violation counts are not exposed through the pup CLI, so those lines always report 'No data available'. Coverage data is fetched via `pup code-coverage branch-summary` and shows 'No data available' only if the query returns nothing.