flake

Track and rerun flaky GitHub Actions CI failures in Remotion issue #8375.

Updated May 15, 2026
One-click install
npx skills add https://github.com/danielbere1973/promoar --skill flake-danielbere1973
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flake
Source: https://github.com/danielbere1973/promoar/tree/main/.agents/skills/flake
Command: npx skills add https://github.com/danielbere1973/promoar --skill flake-danielbere1973

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Flaky CI failures in the Remotion repository waste developer time and obscure real regressions. This Skill identifies flaky GitHub Actions failures, records them in a central tracker issue, and reruns the affected jobs so pull requests can proceed. ## Core Features & Use Cases - Failure Discovery: Inspect PR checks, workflow runs, and job logs via the GitHub CLI to locate failed steps, even when no PR number is provided. - Flake Classification: Distinguish genuine flakes (timeouts, network errors, reruns that pass) from deterministic failures like type errors or broken assertions. - Tracker Maintenance: Add or increment signature rows in issue #8375 with counts, first-seen dates, and evidence links. - Job Reruns: Rerun only failed jobs, cancel stuck runs, and report remaining checks. - Use Case: A contributor sees the "Install and Test" workflow fail on their PR with a fetch failed error. The Skill confirms it is a known flake, increments its count in the tracker, and reruns the failed job. ## Quick Start Run the flake skill to investigate the failing CI check on my Remotion pull request, record it in the flake tracker, and rerun the failed job.

Frequently Asked Questions about flake

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

FAQPage Schema
How do I track flaky CI tests in GitHub Actions?▼

Use the GitHub CLI to inspect failed workflow runs and job logs, extract a stable failure signature, and record it in a central tracker issue. This Skill maintains issue #8375 in the Remotion repository, incrementing counts for repeated signatures and appending new rows with evidence links.

How to rerun only failed jobs in a GitHub Actions workflow?▼

Run `gh run rerun <run-id> --failed` to rerun only the failed jobs in a workflow run. For a single known flaky job in a completed run, use the API endpoint `gh api --method POST repos/<owner>/<repo>/actions/jobs/<job-id>/rerun`.

How do I tell if a CI failure is a flake or a real bug?▼

A failure is likely a flake if it passes on rerun without code changes, involves network or infrastructure errors like `fetch failed`, or is a timeout, race, or browser disconnect unrelated to the PR changes. Deterministic type errors, lint failures, and assertion failures from changed behavior are not flakes.

Can this Skill find failed CI checks without a PR number?▼

Yes. It lists recent open PRs with their check status and recent failed runs of the "Install and Test" workflow using `gh pr list` and `gh run list`, then drills into the relevant run and job logs.

What makes a good flake signature for tracking?▼

A good signature includes the package or suite, the test name, and the root error text with timestamps, paths, ports, and ANSI codes stripped out. This groups repeats of the same flake while staying specific enough to act on.