ci-first-fail
Skill3 starsChanged 4 days agoMITView on GitHub
Buildkite-style first-fail CI annotations. Name the failing STEP before reading logs. Missing required contexts → GitHub Status, not a code blame. Do not migrate this public repo off GitHub Actions. Trigger: red CI, BLOCKED PR wall, "is it the runner", first failing step, Buildkite. Slash: /ci-first-fail.
In this repository153 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hermes-mobile/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agent-automations.mdcCursor rule
- .cursor/rules/agent-device.mdcCursor rule
- .cursor/rules/agent-harness-router.mdcCursor rule
- .cursor/rules/agent-skills-overview.mdcCursor rule
- .cursor/rules/always-agent-mode.mdcCursor rule
- .cursor/rules/callstack-agent-skills-overview.mdcCursor rule
- .cursor/rules/callstack-react-native-best-practices.mdcCursor rule
- .cursor/rules/codeql-agent-hygiene.mdcCursor rule
- .cursor/rules/decision-stack.mdcCursor rule
- .cursor/rules/expo-credit-budget.mdcCursor rule
- .cursor/rules/fleet-repo-intelligence.mdcCursor rule
- .cursor/rules/hermes-mobile-prevention-july-2026.mdcCursor rule
- .cursor/rules/hermes-mobile-real-users.mdcCursor rule
- .cursor/rules/hermes-mobile-verification.mdcCursor rule
- .cursor/rules/no-desktop-hijack.mdcCursor rule
- .cursor/rules/no-manual-handoffs.mdcCursor rule
- .cursor/rules/obsidian-teammate-collaboration.mdcCursor rule
- .cursor/rules/prefer-headless-background-ops.mdcCursor rule
- .cursor/rules/react-native-best-practices.mdcCursor rule
- public/llms.txtllms.txt
- advertise-thumbgate-github-marketplaceSkill
- agent-harness-routerSkill
- agentic-pattern-selectorSkill
- agents-judgment-calls-gateSkill
- ai-native-sdlcSkill
- android-dev-summit-26-gateSkill
- anti-babysitting-mandateSkill
- anti-babysittingSkill
- background-agent-hold-gateSkill
- browseros-agent-harnessSkill
- webmcp-agent-readinessSkill
- ci-pr-monitorSkill
- cloudflare-developer-stackSkill
- cloudflare-kitesurf-browserSkill
- cloudflare-monetization-gatewaySkill
- confidence-offer-gateSkill
- content-laneSkill
- context-six-blockSkill
- context-vaultSkill
- context-weight-gateSkill
- dual-model-agentic-graphragSkill
- egm-fresh-reviewSkill
- elevenlabs-voice-agentsSkill
- emeans-quant-and-instinctSkill
- explainx-trending-honestSkill
- explainx-trending-ragSkill
- future-agi-self-healing-engineSkill
- garryslist-opportunity-trackerSkill
- gemini-decisions-hold-gateSkill
- git-at-scaleSkill
- gitbutler-fleet-automationsSkill
- gitbutler-google-ssoSkill
- gitbutler-mcp-isolatedSkill
- gitbutler-session-absorbSkill
- git-hooks-no-huskySkill
- github-marketplace-action-publishSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Not affiliated. Do not switch vendors.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CI first-fail (Buildkite process steal)
Source: buildkite.com/home (2026-08-18). Not affiliated. Do not switch vendors.
Buildkite's own comparison: stay on GitHub Actions when repos are public and
CI is not costing time or money. This repo is public; required checks are 7
GHA contexts on ubuntu-latest.
What we steal
| Buildkite | Here |
| Step-level visibility / annotations | bin/ci-first-fail --pr N names the first failed step |
| Token-optimized pipeline reads | gh run view --json jobs only — never --log-failed |
| Test identity | first TAP not ok from check annotations, not logs |
| Missing vs failing | absent required → githubstatus.com JSON, not a code blame |
What we do not steal
Pipelines SaaS, Test Engine auto-quarantine, Package Registries, Mobile
Delivery Cloud, MCP server, hosted Mac agents, or a second CI bill.
Auto-quarantine on first fail hides real regressions (--quarantine refused).
Run
node tools/ci-first-fail.js --pr 1819 --json
bin/ci-first-fail --fixture tests/fixtures/ci-first-fail.jsonThen run the failing step's command locally. Complements /diagnose-ci-failure-fast
(still reproduce on origin/main before claiming your regression).
NEVER / ALWAYS
| NEVER | ALWAYS |
| Migrate this repo to Buildkite | Keep the 7 GHA required contexts |
| Dump job logs first | Print first_step |
| Blame code when required contexts are absent | Check githubstatus.com |
gh run rerun a queued run | Wait for Actions to drain |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

