Agent skill · operations · remotion-dev
flake
Track Remotion CI flakes in issue #8375, increment repeated signatures, discover failed PR checks when no PR is given, and rerun flaky GitHub Actions jobs.
Why this skill is useful
Adds specific commands and procedures for tracking and managing CI flakiness in Remotion, which the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. About 4k tokens when loaded. Last updated 2026-08-06. 55,698 stars on the source repository.
What this skill does
Flake Use this skill when a Remotion CI check fails and looks flaky, or when asked to run /flake. Tracker issue: https://github.com/remotion-dev/remotion/issues/8375 Goal Record flaky CI failures in issue #8375 and get the affected suite running again. For every confirmed or likely flake: 1. Identify the PR, workflow run, job, failed step, and concise failure signature. 2. Update issue #8375: If the signature already exists, increment its Count. If it is new, insert a row with count 1, workflow/job, first-seen date, and evidence URL. Sort all rows by numeric Count in descending order after every addition or increment, preserving the existing order for equal counts. 3. Rerun the flaky job or failed jobs. Find The Failure Prefer gh because the GitHub app may not expose all Actions logs or write permissions. If the user gave a PR: If the user gave a workflow run or job URL: If there is no PR context, inspect recent open PRs and recent failed runs: For rerun attempts, inspect the original attempt before deciding whether a failure was flaky: Classify A Flake Treat a failure as a flake when at least one is true: The same run, job, or failed step succeeded after a rerun without code changes. The failure is infrastructure/network related, such as fetch failed, connection resets, package manager download failures, cache service failures, or runner provisioning errors. The test failure is a timeout, race, browser disconnect, port collision, or intermittent external service failure, and the PR changes do not plausibly touch that area. Do not record deterministic type errors, lint errors, snapshots, or test assertions caused by changed source behavior unless there is evidence they pass on retry. Signature Rules Use a stable signature that groups repeats but stays specific enough to act on: Include package or suite when available, for example @remotion/it-tests#testssr. Include test name when available. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills remotion-dev/flake