skills.rest
naxoruto
naxorutoCOMMUNITY
Explore all skills by this author →
GitHub

test-flakiness

Analyze CI logs and test histories to detect flaky tests.

Updated Aug 27, 2026
Search Tags:#debugging#flaky-tests#quarantine#test-results#ci-logs#regression-suite
One-click install
npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill test-flakiness-naxoruto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-flakiness
Source: https://github.com/naxoruto/TE-limonchero-3d/tree/main/.claude/skills/test-flakiness
Command: npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill test-flakiness-naxoruto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect flaky tests by identifying non-deterministic test behavior in CI logs and test histories, aggregating per-test pass rates, and flagging intermittent failures to prevent misleading CI signals and unstable releases.

Core Features & Use Cases

  • Aggregate per-test pass/fail history from CI logs and test results to reveal instability.
  • Classify flaky tests by likely root causes (timing/async, order dependency, random seeds, resource leaks, external state, float comparisons, load races).
  • Recommend actionable remediation (quarantine guidance, root-cause investigation, and updates to the regression suite).
  • Maintain a flaky-test registry and update regression suite entries with remediation status and notes.

Quick Start

Run /test-flakiness scan to analyse 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 detect flaky tests in my CI pipeline logs?▼

To detect flaky tests, this skill aggregates per-test pass/fail histories from CI logs to reveal non-deterministic test behavior. It scans GitHub Actions logs and local test results to identify intermittent failures.

What are the common root causes of flaky tests in a regression suite?▼

Common root causes of flaky tests include timing and async issues, order dependencies, random seeds, resource leaks, external state, float comparisons, and load races. The skill classifies flaky tests by these likely root causes.

How do I quarantine flaky tests to stabilize CI signals?▼

You can quarantine flaky tests by using the proposed quarantine guidance provided by the skill. It maintains a flaky-test registry and updates regression suite entries with remediation status to prevent misleading CI signals.

Does this tool work with GitHub Actions logs and local test-result histories?▼

Yes, this tool works with GitHub Actions logs, local logs, and test-result histories. It aggregates pass/fail data across these sources to enforce flakiness thresholds and output guidance for your regression suite.

What is the best way to update a regression suite after identifying non-deterministic test behavior?▼

The best way to update a regression suite is to apply the suggested code changes and quarantine guidance generated by the analysis. The skill maintains a flaky-test registry and outputs actionable remediation to update suite entries.

Related Skills

Explore More Software Engineering Skills→
jmaglyjmagly
175

flaky-detect

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

Community
Advanced
sumilee-pcusumilee-pcu

test-flakiness

Detect non-deterministic test failures by analyzing CI logs and test artifacts.

Community
Advanced
cenconq25cenconq25
39

test-flakiness

Parse CI run histories to compute per-test pass rates and maintain a flaky-test registry.

Community
Advanced
Negentropy-LabyNegentropy-Laby
3

test-flakiness

Analyze CI logs and test histories to identify intermittent failures.

Official
Advanced