skills.rest
Negentropy-Laby
Negentropy-LabyOFFICIAL
Explore all skills by this author →
GitHub

test-flakiness

Analyze CI logs and test histories to identify intermittent failures.

3|Updated Jun 3, 2026
Search Tags:#automation#testing#logs#regression#ci#flaky
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill test-flakiness-negentropy-laby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-flakiness
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/test-flakiness
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill test-flakiness-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects non-deterministic (flaky) tests by analyzing CI run logs or test histories to identify intermittent failures and provide remediation guidance.

Core Features & Use Cases

  • Parses CI logs from popular CI systems (GitHub Actions, GitLab CI, local pipelines)
  • Aggregates per-test pass rates, flags intermittent failures, and recommends quarantine or fixes
  • Generates a regression-ready report and keeps a flaky-test registry for tracking

Quick Start

Run the /test-flakiness [ci-log-path | scan | registry] command to start analyzing flaky tests immediately.

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 in my CI workflow?▼

You can identify flaky tests by parsing CI logs and test histories to detect intermittent failures across multiple runs. This process aggregates per-test pass rates, flags non-deterministic behavior, and produces a regression plan to guide fixes.

What causes intermittent test failures in CI pipelines?▼

Intermittent test failures in CI pipelines are caused by non-deterministic tests, known as flaky tests. Analyzing multi-run CI workflows helps surface these failures by tracking pass rates and identifying quarantine candidates.

Does this flaky test detection work with GitHub Actions and GitLab CI?▼

Yes, flaky test detection works with GitHub Actions, GitLab CI, and local test suites. It parses logs from these CI systems to aggregate per-test results and flag intermittent failures across multi-run workflows.

How do I generate a regression plan for intermittent test failures?▼

You generate a regression plan for intermittent test failures by analyzing CI logs to produce per-test results and recommendations. This process outputs a regression-ready report and maintains a flaky-test registry for tracking.

When should I quarantine flaky tests instead of fixing them immediately?▼

You should quarantine flaky tests when intermittent failures disrupt CI workflows but immediate fixes are not feasible. Analyzing test histories recommends quarantine candidates, keeping a flaky-test registry while a regression plan guides fixes.

Related Skills

Explore More Software Engineering Skills→
jmaglyjmagly
175

flaky-detect

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

Community
Advanced
HechaoYannetHechaoYannet

test-flakiness

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

Community
Advanced
packetalienpacketalien

test-flakiness

Analyze CI run logs and test histories to detect flaky tests.

Community
Intermediate
MichaelSolatiMichaelSolati

test-flakiness

Parse CI logs and JUnit XML to detect flaky tests and classify root causes.

Community
Advanced