
Triage Ci Flake
This handles the tedious workflow of debugging flaky CI tests that mysteriously fail on main but pass locally. When you point it at a failing test or PR, it systematically reproduces the issue by running the specific test against both dev and production builds, not just reading logs and guessing. The PR aggregation feature is clever: it pulls all failing checks from a PR number, extracts the actual test names and errors, then patterns across them to spot if it's a selector change breaking multiple suites or isolated flakiness. The source is adamant about mandatory reproduction steps before any fixes, which is the right instinct. Worth using when you're staring at a red CI check wondering if it's timing, bundling, or test pollution causing the failure.
- skills.sh installs
- 307
- GitHub stars
- 45.7K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add payloadcms/payload --skill triage-ci-flake --agent claude-codeInstalls into .claude/skills of the current project.
Files
Triage CI Failure
Overview
Systematic workflow designed specifically for triaging and fixing end-to-end (e2e) test failures in CI, especially flaky Playwright tests that pass locally but fail in CI. E2E tests that made it to main are usually flaky due to timing, bundling, or environment differences.
CRITICAL RULE: You MUST run the reproduction workflow before proposing any fixes. No exceptions.
When to Use
- CI test fails on
mainbranch after PR was merged - Test passes locally but fails in CI
- Test failure labeled as "flaky" or intermittent
- E2E test timing out in CI only
- User provides a PR URL/number with failing checks
PR-Based Workflow (When PR URL/Number Provided)
When the user provides a PR URL (e.g., https://github.com/payloadcms/payload/pull/16701) or PR number:
Step 1: Fetch PR Status Checks
First, use tool_search with query "github pull request status checks" to load the GitHub tools.
Then use the github-pull-request_pullRequestStatusChecks tool to get all failing checks:
Sponsors
Details
- Repository
- github.com/payloadcms/payload
- Categories
- Backend & APIs, Testing & QA, DevOps & CI/CD, Git & Pull Requests
- First seen
- Jun 3, 2026