keel-flake-audit

Detect intermittently failing tests and track them as issues.

4|Updated May 23, 2026
One-click install
npx skills add https://github.com/berkayturanci/keel --skill keel-flake-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: keel-flake-audit
Source: https://github.com/berkayturanci/keel/tree/main/.agents/skills/keel-flake-audit
Command: npx skills add https://github.com/berkayturanci/keel --skill keel-flake-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies intermittent test failures and tracks them as individual issues, streamlining the process of fixing flaky tests in software projects.

Core Features & Use Cases

  • Flake Detection: Automatically detects tests that intermittently pass and fail.
  • Issue Tracking: Opens new issues for each new detected flake.
  • Integration: Integrates with existing CI systems and can run locally for fallback.
  • Use Case: Ideal for projects with complex test suites where flaky tests are a common issue.

Quick Start

Run the keel-flake-audit skill to scan for flaky tests in your project's current CI history.

Frequently Asked Questions about keel-flake-audit

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

FAQPage Schema
How do I automatically detect and track intermittently failing tests?

Automatically detecting intermittently failing tests requires analyzing test history to identify flaky behavior and classifying those tests for issue creation. This streamlines the process of fixing unstable tests in complex software projects.

How does flake detection work with CI integration?

Flake detection works with CI integration by scanning your project's current CI history to identify tests that intermittently pass and fail. It also provides fallback to local test runs if CI integration is unavailable.

Can I run flake detection locally instead of using CI systems?

Yes, you can run flake detection locally instead of using CI systems. The skill provides a fallback to local test runs, allowing you to identify intermittently failing tests outside of your CI environment.

What is the best way to manage issue tracking for flaky tests?

The best way to manage issue tracking for flaky tests is to automatically classify detected flakes based on test history and open new issues for each one. This ensures individual flaky tests are tracked until resolved.

When should I use automated flake detection for my test suite?

You should use automated flake detection for your test suite when working on projects with complex test suites where flaky tests are a common issue. It identifies intermittent failures and tracks them as individual issues.