ci-investigate

Analyze flaky CI failures across CircleCI and GitHub Actions runs.

23|4|Updated Sep 5, 2013
One-click install
npx skills add https://github.com/drn/dots --skill ci-investigate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-investigate
Source: https://github.com/drn/dots/tree/main/agents/skills/ci-investigate
Command: npx skills add https://github.com/drn/dots --skill ci-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers quickly identify the root causes of intermittent failures in Continuous Integration (CI) pipelines, saving significant debugging time and improving code stability.

Core Features & Use Cases

  • Automated Failure Analysis: Fetches and analyzes multiple CI runs to pinpoint flaky tests or infrastructure issues.
  • Pattern Identification: Categorizes failures (e.g., timing, isolation, infrastructure) to suggest targeted fixes.
  • Use Case: When your CI pipeline starts failing intermittently on a specific test suite, use this Skill to analyze the last 10 runs, identify the flaky test, and get a proposed fix.

Quick Start

Investigate the most recent CI failures on the current branch.

Frequently Asked Questions about ci-investigate

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

FAQPage Schema
How do I debug flaky CI tests across multiple workflow runs?

To debug flaky CI tests across multiple workflow runs, you analyze job logs and test results to identify patterns. This process categorizes root causes like deterministic bugs, timing issues, parallel collisions, or infrastructure problems to propose targeted fixes.

What causes intermittent failures in GitHub Actions or CircleCI pipelines?

Intermittent failures in GitHub Actions or CircleCI pipelines are caused by deterministic bugs, timing issues, parallel collisions, or infrastructure problems. Analyzing multiple workflow runs categorizes these specific root causes.

Do I need the gh CLI to investigate CircleCI flaky tests?

You need the gh CLI to investigate GitHub Actions failures, while CircleCI investigations require CircleCI MCP tools. These dependencies retrieve workflow data, parse job logs, and classify test failures.

How do I identify patterns in intermittent CI pipeline failures?

You identify patterns in intermittent CI pipeline failures by fetching and analyzing multiple workflow runs. Parsing job logs and test results categorizes failures like timing issues or infrastructure problems to suggest targeted fixes.

Can I analyze the last 10 CI runs to find a flaky test fix?

You can analyze the last 10 CI runs to find a flaky test fix by fetching job logs and test results. This automates pattern identification across workflow runs to categorize root causes and propose fixes.