Agent skill

CI Fix

Scan all CI builds and tests, find failures, fetch error logs, and fix the code.

MITAuto-check passedTesting & QA

Install CI Fix

skills CLI

$ npx skills add FastLED/FastLED --skill ci-fix -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install FastLED/FastLED ci-fix --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/FastLED/FastLED.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ci-fix .claude/skills/ci-fix && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "ci-fix" agent skill from https://github.com/FastLED/FastLED/tree/master/.claude/skills/ci-fix into .claude/skills/ci-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-fix", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/FastLED/FastLED/tree/master/.claude/skills/ci-fix

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add FastLED/FastLED --skill ci-fix -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install FastLED/FastLED ci-fix --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FastLED/FastLED.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/ci-fix .agents/skills/ci-fix && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ci-fix" agent skill from https://github.com/FastLED/FastLED/tree/master/.claude/skills/ci-fix into .agents/skills/ci-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-fix", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add FastLED/FastLED --skill ci-fix -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install FastLED/FastLED ci-fix --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FastLED/FastLED.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/ci-fix .cursor/skills/ci-fix && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ci-fix" agent skill from https://github.com/FastLED/FastLED/tree/master/.claude/skills/ci-fix into .cursor/skills/ci-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-fix", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/FastLED/FastLED.git --path .claude/skills/ci-fix

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add FastLED/FastLED --skill ci-fix -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install FastLED/FastLED ci-fix --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FastLED/FastLED.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/ci-fix .gemini/skills/ci-fix && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ci-fix" agent skill from https://github.com/FastLED/FastLED/tree/master/.claude/skills/ci-fix into .gemini/skills/ci-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-fix", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install FastLED/FastLED ci-fix

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add FastLED/FastLED --skill ci-fix -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/FastLED/FastLED.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/ci-fix .github/skills/ci-fix && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ci-fix" agent skill from https://github.com/FastLED/FastLED/tree/master/.claude/skills/ci-fix into .github/skills/ci-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-fix", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add FastLED/FastLED --skill ci-fix -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install FastLED/FastLED ci-fix --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FastLED/FastLED.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/ci-fix .opencode/skills/ci-fix && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ci-fix" agent skill from https://github.com/FastLED/FastLED/tree/master/.claude/skills/ci-fix into .opencode/skills/ci-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-fix", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ci-fix
GitHub stars: 7.5k
Token cost: ~897 tokens
SKILL.md length: 449 words
Files: 1
Skills in repo: 23
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Scan all CI builds and tests, find failures, fetch error logs, and fix the code.

Works in 4 steps: Scan builds and get error logs → Analyze and prioritize → For each failing test or build → …
CI is red and you need to diagnose and repair build/test failures
SKILL.md covers Step 1: Scan builds and get…, Step 2: Analyze and prioritize, Step 3: For each failing test… and Step 4: Verify fixes don't…, plus 1 more section
Calls bash and uv

What it does

CI Fix is an agent skill from FastLED/FastLED. Scan all CI builds and tests, find failures, fetch error logs, and fix the code. Prioritizes unit tests, example tests, then uno, attiny85, esp32s3, esp32c6, teensy41. Use when CI is red and you need to diagnose and repair build/test failures.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Failing and flaky tests and Unit testing. It works with Bash. The repository describes itself as: The FastLED library for colored LED animation on Arduino. Please direct questions/requests for help to the FastLED Reddit community: http://fastled.io/r We'd like to use github… The licence is MIT.

When your agent uses it

CI is red and you need to diagnose and repair build/test failures
Tasks that involve Failing and flaky tests
Tasks that involve Unit testing

Example prompts

“/ci-fix”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Scan builds and get error logs
Analyze and prioritize
For each failing test or build
Verify fixes don't break other platforms

What it can do on your machine

Read from SKILL.md and the folder at commit ce225ed. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- bash
- uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

CI Fix loads about 897 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 449 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~63
When it runs · the whole SKILL.md, loaded when a task matches: ~897

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FastLED/FastLED at commit ce225ed, republished under its MIT licence (© FastLED). 449 words, ~897 tokens.

Download SKILL.mdSave it as .claude/skills/ci-fix/SKILL.md (or your agent's skills folder).

name: ci-fix
description: Scan all CI builds and tests, find failures, fetch error logs, and fix the code. Prioritizes unit tests, example tests, then uno, attiny85, esp32s3, esp32c6, teensy41. Use when CI is red and you need to diagnose and repair build/test failures.
argument-hint: [--board <name>] [--all]
context: fork

Find and fix CI build and test failures across all platforms.

Arguments: $ARGUMENTS

Step 1: Scan builds and get error logs

Run the CI build scanner to discover all failing builds and tests with error context:

bash

uv run ci/tools/gh/ci_builds.py --errors $ARGUMENTS

This auto-discovers workflows from .github/workflows/ matching build_*.yml, unit_test_*.yml, and example_test_*.yml. Adding a new workflow file automatically adds it to this report.

Step 2: Analyze and prioritize

Review the output. Builds are already sorted by priority:

unit tests — unit_test_linux, unit_test_macos, unit_test_windows — fix first, these validate core logic
example tests — example_test_linux, example_test_macos, example_test_windows — validate example compilation
uno — AVR 8-bit, most constrained, most users
attiny85 — AVR tiny, extreme flash/RAM constraints
esp32s3 — ESP32-S3, primary ESP target
esp32c6 — ESP32-C6, RISC-V ESP target
teensy41 — Teensy 4.1, ARM Cortex-M7
Everything else — alphabetical within non-priority builds

Fix priority builds first. If --board <name> was passed, focus only on those.

Step 3: For each failing test or build

For unit test failures:

Read the error logs from the scan output
Run the failing test(s) locally: bash test or bash test <TestName>
If a test fails, re-run in debug mode: bash test <TestName> --debug
Identify the root cause and fix the source code or test
Verify: bash test

For example test failures:

Read the error logs from the scan output
Run the failing example(s) locally: bash compile wasm --examples <ExampleName>
Identify the root cause (missing include, type error, API change, etc.)
Fix the source or example code
Verify: bash compile wasm --examples <ExampleName>

Show full SKILL.md (192 more words)Show less

For board build failures:

Read the error logs from the scan output
Identify the root cause (missing header, type error, platform ifdef, linker error, etc.)
Find the relevant source file(s) and read them
Make the fix — prefer the simplest change that fixes the error:
- Missing platform guard → add #ifdef / #if defined()
- Missing include → add the include
- Type mismatch → fix the type
- API difference → use conditional compilation
After fixing, verify by compiling: bash compile <board> --examples Blink (use the board arg from the scan output, e.g. bash compile uno --examples Blink)

Step 4: Verify fixes don't break other platforms

After fixing a failing build, consider whether the change could break other platforms. If you changed shared code (not platform-guarded), spot-check by compiling another platform:

bash

bash compile wasm --examples Blink

Notes

The scanner discovers workflows dynamically — no hardcoded list to maintain
Workflow patterns: build_*.yml, unit_test_*.yml, example_test_*.yml
Use --board uno,esp32s3 to focus on specific boards
Use --all flag if you want to see passing builds too (default: only failing with --errors)
Error logs show up to 5 error blocks per build with surrounding context
The priority list is defined in ci/tools/gh/ci_builds.py in the PRIORITY_BOARDS constant

Files

Just SKILL.md in .claude/skills/ci-fix of FastLED/FastLED.

Open the folder on GitHubat commit ce225ed

Compare with similar skills

CI Fix next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

CI Fix compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
CI Fix this skillFastLED/FastLED	7.5k	—	~897	Automated safety check: Pass	MIT	today
Debug Playwright Prowquay/quay	2.8k	—	~2.2k	Automated safety check: Pass	Apache-2.0	today
Quay Prow Triagequay/quay	2.8k	—	~2.9k	Automated safety check: Pass	Apache-2.0	today
Bats Shell Testing Patternswshobson/agents	40k	12 repos	~1.3k	Automated safety check: Pass	MIT	3 days ago
Test Guidelinesgetsentry/sentry-react-native	1.8k	—	~1.3k	Automated safety check: Pass	MIT	today
gtest-parallel Test Runnerwebrtc-sdk/webrtc	446	1 repos	~432	Automated safety check: Pass	BSD-3-Clause	yesterday

Similar skills

Debug Playwright Prow
quay/quay
Deep-dive diagnosis of a Playwright test failure already isolated to one Quay Prow/OpenShift CI run: downloads its GCS artifacts (results.json, JUnit, build/pod logs, Jaeger traces), classifies real…
2.8k GitHub stars~2.2k tokensUpdated today
Testing & QAAuto-check passed
Quay Prow Triage
quay/quay
Diagnose any Quay Prow job failure end to end: prowjob.json - top-level build log - JUnit - resolved failing step - Playwright results.json when the failing step is Playwright, continuing through…
2.8k GitHub stars~2.9k tokensUpdated today
Testing & QAAuto-check passed
Bats Shell Testing Patterns
wshobson/agents
Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.
40k GitHub starsUsed in 12 repos~1.3k tokens
Testing & QAAuto-check passed
Test Guidelines
getsentry/sentry-react-native
Official
Enforce Sentry React Native SDK test conventions for naming, structure, mocking, and fixtures with Jest.
1.8k GitHub stars~1.3k tokensUpdated today
Testing & QAAuto-check passed
gtest-parallel Test Runner
webrtc-sdk/webrtc
Runs Google Test binaries in parallel with gtest-parallel to speed up single-threaded tests, repeat flaky ones and filter specific tests.
446 GitHub starsUsed in 1 repo~432 tokens
Testing & QAAuto-check passed
Ckeditor5 Testing
TriliumNext/Trilium
Testing CKEditor 5 plugins in the Trilium monorepo. An agent skill from TriliumNext/Trilium.
38k GitHub stars~3.3k tokensUpdated today
Testing & QAAuto-check passed

Questions about CI Fix

What does CI Fix do?

Scan all CI builds and tests, find failures, fetch error logs, and fix the code. CI Fix is an agent skill from FastLED/FastLED. Scan all CI builds and tests, find failures, fetch error logs, and fix the code.

When should I use CI Fix?

CI Fix fits situations like: CI is red and you need to diagnose and repair build/test failures; tasks that involve Failing and flaky tests; tasks that involve Unit testing.

How do I install CI Fix in Claude Code?

Run `npx skills add FastLED/FastLED --skill ci-fix -a claude-code`. Or copy the skill folder (.claude/skills/ci-fix in FastLED/FastLED) into .claude/skills/ci-fix in your project. Claude Code loads it when a task matches its description.

How do I install CI Fix in Codex?

Run `npx skills add FastLED/FastLED --skill ci-fix -a codex`. Or copy the skill folder (.claude/skills/ci-fix in FastLED/FastLED) into .agents/skills/ci-fix in your project. Codex loads it when a task matches its description.

Can I use CI Fix in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FastLED/FastLED --skill ci-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ci-fix, .gemini/skills/ci-fix, .github/skills/ci-fix and .opencode/skills/ci-fix in your project.

What does CI Fix need to run?

Going by SKILL.md and its folder, CI Fix needs the command-line tools its instructions call (bash and uv).

Does CI Fix access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is CI Fix safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does CI Fix use?

CI Fix is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does CI Fix use?

About 897 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to CI Fix?

Skills that share tags, products or a category with CI Fix: Debug Playwright Prow (quay/quay, 2.8k stars), Quay Prow Triage (quay/quay, 2.8k stars), Bats Shell Testing Patterns (wshobson/agents, 40k stars) and Test Guidelines (getsentry/sentry-react-native, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CI Fix?

FastLED (a GitHub organization) maintains it in FastLED/FastLED, which has 7,505 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 8, 2026.

Source: FastLED/FastLED on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install CI Fix

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Step 1: Scan builds and get error logs

Step 2: Analyze and prioritize

Step 3: For each failing test or build

For unit test failures:

For example test failures:

For board build failures:

Step 4: Verify fixes don't break other platforms

Notes

Files

Compare with similar skills

Similar skills

More from FastLED/FastLED

Related

Questions about CI Fix