check-upstream-flake

Query Chromium LUCI Analysis for test flakiness statistics and verdicts.

4|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/brave-experiments/brave-core-bot --skill check-upstream-flake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-upstream-flake
Source: https://github.com/brave-experiments/brave-core-bot/tree/main/.claude/skills/check-upstream-flake
Command: npx skills add https://github.com/brave-experiments/brave-core-bot --skill check-upstream-flake

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers quickly determine if a failing test is due to an intermittent issue in the upstream Chromium project, preventing unnecessary debugging efforts on the Brave side.

Core Features & Use Cases

  • LUCI Analysis Query: Checks the Chromium LUCI Analysis database for historical flakiness data of a given test.
  • Verdict & Recommendation: Provides a clear verdict (e.g., "Known upstream flake", "Stable upstream") and actionable recommendations for handling test failures or filter file decisions.
  • Use Case: When a test fails in Brave's CI, use this Skill to check if it's a known flake in Chromium. If it is, you can confidently add it to the filter file, saving significant debugging time.

Quick Start

Use the check-upstream-flake skill to check if the test 'WebUIURLLoaderFactoryTest.RangeRequest' is flaky upstream.

Frequently Asked Questions about check-upstream-flake

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

FAQPage Schema
How do I check if a failing Chromium test is flaky upstream?

To check if a failing Chromium test is flaky upstream, query the LUCI Analysis database for historical pass/fail/flake statistics. This Skill provides a clear verdict on upstream stability and actionable recommendations for filter file decisions.

What is upstream test flakiness and when should I investigate it?

Upstream test flakiness refers to intermittent test failures originating in the Chromium project. You should investigate it when a test fails in your CI, using LUCI Analysis to determine if the failure is a known upstream flake or a local issue requiring debugging.

Can I get JSON output from LUCI Analysis for programmatic CI integration?

Yes, you can get JSON output from LUCI Analysis queries for programmatic integration. This Skill supports returning historical flakiness statistics and stability verdicts in JSON format, allowing automated workflows to evaluate upstream test stability.

How do I use LUCI Analysis to decide whether to add a test to a filter file?

Use LUCI Analysis to query historical flakiness data for the specific test. The Skill provides a verdict such as "Known upstream flake" or "Stable upstream" alongside actionable recommendations, giving you confidence to add it to the filter file or investigate further.

Does this approach support custom lookback periods for historical flakiness data?

Yes, this approach supports various lookback periods to assess historical flakiness data. By querying the Chromium LUCI Analysis database over different time ranges, you receive pass/fail statistics and a stability verdict tailored to that specific duration.