agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.agents/skills/ci-first-fail/SKILL.md

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.

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
  1. Distinctive:

    Not affiliated. Do not switch vendors.

    line 13

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

BuildkiteHere
Step-level visibility / annotationsbin/ci-first-fail --pr N names the first failed step
Token-optimized pipeline readsgh run view --json jobs only — never --log-failed
Test identityfirst TAP not ok from check annotations, not logs
Missing vs failingabsent 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.json

Then run the failing step's command locally. Complements /diagnose-ci-failure-fast (still reproduce on origin/main before claiming your regression).

NEVER / ALWAYS

NEVERALWAYS
Migrate this repo to BuildkiteKeep the 7 GHA required contexts
Dump job logs firstPrint first_step
Blame code when required contexts are absentCheck githubstatus.com
gh run rerun a queued runWait for Actions to drain

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.