triage-ci-flake
A structured workflow for investigating and fixing CI test failures and flaky tests on the main branch.
Install
mkdir -p .claude/skills/triage-ci-flake && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6235" && unzip -o skill.zip -d .claude/skills/triage-ci-flake && rm skill.zipInstalls to .claude/skills/triage-ci-flake
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing testsKey capabilities
- →Aggregate failing CI status checks
- →Fetch PR-specific test logs
- →Categorize intermittent test failures
- →Generate summary tables of failed suites
How it works
It queries GitHub's PR status checks API to extract failing test IDs, then scrapes logs to consolidate error patterns into a categorized format.
Inputs & outputs
When to use triage-ci-flake
- →Investigating CI failures after PR merge
- →Triaging intermittent flaky tests
- →Summarizing failing test suites for PRs
About triage-ci-flake
Provides a consistent process for triaging CI failures, specifically for tests passing locally but failing in environments. It automates the retrieval of PR status checks, aggregates test failures, and mandates reproduction workflows.
Use when CI tests fail on main branch after PR merge, or when investigating flaky test failures in CI environments
When not to use it
- →Direct local bug fixing without CI reproduction
- →Non-PR related code errors
Prerequisites
Limitations
- →Depends on availability of remote logs
- →Limited to PRs with configured status checks
How it compares
It mandates a reproduction workflow as a hard rule, preventing guesses at the root cause of flaky tests.
Compared to similar skills
triage-ci-flake side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| triage-ci-flake (this skill) | 1 | 4mo | Review | Intermediate |
| analyze-failures | 1 | 8mo | Caution | Intermediate |
| moai-workflow-testing | 1 | 3mo | Review | Intermediate |
| debug-ci | 1 | 8mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by payloadcms
View all by payloadcms →You might also like
analyze-failures
saleor
Analyze Playwright E2E test failure reports from CI. Parses merged blob reports, groups similar errors, and delegates to specialized subagents for investigation and fixes. Use when CI tests fail or when asked to fix E2E test failures.
moai-workflow-testing
modu-ai
Comprehensive development workflow specialist combining DDD testing, debugging, performance optimization, code review, PR review, and quality assurance into unified development workflows
debug-ci
Sovereign-Labs
Debug failed CI tests by fetching workflow logs from GitHub Actions and analyzing failures. Use when the user mentions CI failures, test failures, or wants to understand why their PR's CI is failing.
cts-triage
gfx-rs
Run CTS test suites and investigate failures
detect-flaky-tests
Sovereign-Labs
Identify flaky tests by comparing failures across multiple CI runs. Use when the user suspects flaky tests, sees intermittent failures, or wants to analyze test reliability.
ci-loop
hyodotdev
Run the full CI pipeline locally and iterate until all tests pass.