skills.rest
mui
muiOFFICIAL
Explore all skills by this author →
Website𝕏@MUI_hqGitHub

circleci-why-flaky

Classify CircleCI workflow failures by root cause into flakes, outages, or bugs.

106|36|Updated Mar 28, 2020
Search Tags:#debugging#logs#api#workflows#ci#flaky#circleci
One-click install
npx skills add https://github.com/mui/mui-public --skill circleci-why-flaky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: circleci-why-flaky
Source: https://github.com/mui/mui-public/tree/main/.claude/skills/circleci-why-flaky
Command: npx skills add https://github.com/mui/mui-public --skill circleci-why-flaky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bucket recent CircleCI failures by root cause and tell the user which buckets are fixable flake, external outage, or real bug. Infers project + branch from the current git repo; defaults to last 7 days.

Core Features & Use Cases

  • Bucket recent CircleCI failures by root cause and tell the user which buckets are fixable flake, external outage, or real bug.
  • Infers project + branch from the current git repo; defaults to last 7 days.
  • Outputs a structured layout of summary and per-failed-job logs to assist debugging.

Quick Start

Run the fetch script to pull recent CircleCI failures into a ready-to-classify directory.

Frequently Asked Questions about circleci-why-flaky

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

FAQPage Schema
How do I classify CircleCI workflow failures by root cause?▼

To classify CircleCI workflow failures by root cause, this Skill infers your project, organization, and branch, then collects recent pipelines and failed jobs to separate fixable flakes from real bugs. It outputs structured per-job logs and a summary for downstream debugging.

How can I separate CircleCI flakes from real bugs?▼

You can separate CircleCI flakes from real bugs by analyzing recent workflow failures. This Skill buckets failures into categories like fixable flake, external outage, or real bug, using CircleCI API calls to generate machine-readable logs for classification.

Does this CircleCI failure classifier require authentication?▼

This CircleCI failure classifier uses CircleCI API calls with optional authentication. It infers the project and branch from your current git repository and defaults to analyzing the last 7 days of pipeline data.

What is the best way to debug CircleCI flaky tests?▼

The best way to debug CircleCI flaky tests is to collect recent failed job logs into a structured, machine-readable format. This Skill automates that process, generating a per-job log layout and a summary to assist debugging and root cause analysis.

Why are my CircleCI workflows failing intermittently?▼

Your CircleCI workflows may be failing intermittently due to fixable flakes or external outages. This Skill analyzes recent pipeline failures to bucket them by root cause, helping you determine if the failures are real bugs or temporary infrastructure issues.

Related Skills

Explore More Software Engineering Skills→
iani-kuliiani-kuli

github-auth

Configure GitHub authentication via gh CLI or Git credential helpers.

Community
Intermediate
Pear-CommercePear-Commerce

tech-log-test-failure-watcher

Monitor Slack #tech-log for api.pearcommerce.com test failures and triage them.

Official
Advanced
u9401066u9401066

git-pusher

Automate Git commit, push, and CI workflow triggering with pre-push validation.

Community
Intermediate
drndrn
23

ci-investigate

Analyze flaky CI failures across CircleCI and GitHub Actions runs.

Community
Advanced