skills.rest
HechaoYannet
HechaoYannetCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-flakiness

Analyze CI logs to compute per-test pass rates and flag flaky tests.

Updated Apr 8, 2026
Search Tags:#logs#regression#ci#flaky#quarantine#test-results
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill test-flakiness-hechaoyannet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-flakiness
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/test-flakiness
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill test-flakiness-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect flaky tests by analyzing CI run logs and historical test results, identifying intermittent failures and guiding quarantine or fixes.

Core Features & Use Cases

  • Reads CI logs from GitHub Actions, Jenkins, and other pipelines to compute per-test pass rates.
  • Flags flaky tests and recommends remediation steps, including quarantine or targeted fixes.
  • Maintains a flaky test registry and produces a report to inform regression management.

Quick Start

Run /test-flakiness scan to analyze all available CI logs and identify flaky tests.

Frequently Asked Questions about test-flakiness

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

FAQPage Schema
How do I identify flaky tests from CI logs across different pipelines?▼

Detecting flaky tests involves parsing JUnit-like XML or plain text CI logs from GitHub Actions, Jenkins, and other pipelines. The system computes per-test pass rates across historical runs to flag intermittent failures that alternate pass and fail, suggesting quarantine or fixes.

What is the best way to track intermittent test failures in a regression registry?▼

Tracking intermittent test failures in a regression registry is done by computing per-test pass rates from historical CI test results. The system flags flaky tests and outputs a quarantine-ready report to maintain and inform your regression management strategy.

Does this flaky test detection work with Jenkins and GitHub Actions test results?▼

Yes, this flaky test detection works with GitHub Actions, Jenkins, and other CI systems. It analyzes historical logs or test results from these pipelines to compute pass rates and flag intermittent failures for quarantine or regression management.

How do I generate a quarantine-ready report for intermittent CI test failures?▼

Generating a quarantine-ready report for intermittent CI test failures requires analyzing historical test results to compute per-test pass rates. The system flags flaky tests that alternate pass and fail, outputting a report and updating your regression registry.

Can I parse plain text CI logs to compute pass rates for flaky tests?▼

Yes, you can parse plain text CI logs or JUnit-like XML to compute pass rates for flaky tests. The system analyzes these historical logs to identify intermittent failures and recommend remediation steps like quarantine or fixes.

Related Skills

Explore More Software Engineering Skills→
polsegupolsegu

test-flakiness

Detect nondeterministic failures by parsing CI logs and aggregating per-test pass/fail histories.

Community
Intermediate
jmaglyjmagly
175

flaky-detect

Analyze CI history and test execution patterns to identify flaky tests.

Community
Advanced
DevelopersGlobalDevelopersGlobal
65

ci-cd-pipelines

Automate CI/CD pipelines with quality gates and deployment processes.

Official
Advanced
XGanQAQXGanQAQ
1

test-flakiness

Analyze CI test logs to detect intermittent PASS/FAIL flaky tests.

Community
Advanced