agentleFS
IgorGanapolskyIgorGanapolsky/ThumbGate/.agents/skills/ci-gha-buildkite-patterns-not-clone/SKILL.md

ci-gha-buildkite-patterns-not-clone

Skill29 starsChanged 7 months agoMITView on GitHub

Buildkite pipeline architecture is FORMAT, not a ThumbGate CI vendor. Steal first-fail step identity, PR fail-fast, needs:/wait honesty, skip conditions, and GITHUB_STEP_SUMMARY annotations onto existing GitHub Actions. Never add Buildkite Pipelines, agents, Test Engine, or a second required check. Slash: /ci-gha-buildkite-patterns-not-clone.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never migrate this public repo to Buildkite.

    line 30
  2. Very specific:

    Do not vendor buildkite-agent.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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 GHA Buildkite patterns — compare, do not clone

Goal

Fail-closed GitHub Actions diagnosis for whom: ThumbGate public CI — so a red PR names the first failed step, cancels leftover PR runs, and never grows a Buildkite bill.

Constraints

NEVERALWAYS
Migrate this public repo to BuildkiteKeep the required GHA contexts on ubuntu-latest
Dump --log-failed firstnpx thumbgate ci-gha-buildkite-patterns --jobs-json=…
gh run rerun a queued jobWait for Actions to drain
Test Engine auto-quarantineFirst fail is a regression until proven otherwise
cancel-in-progress: true on mainCancel PR reruns only

HARD fail closed. REFUSE SKU clones. This is not a Buildkite clone. Never migrate this public repo to Buildkite.

Reference

Examples (show, don't tell)

Weak: "Buildkite is faster, add it as a required check."

Gold:

$ npx thumbgate ci-gha-buildkite-patterns --json --map-only
ok: true
$ npx thumbgate ci-gha-buildkite-patterns --json --migrate
ok: false  # migrate_vendor

Procedures

npx thumbgate ci-gha-buildkite-patterns --json --map-only
npx thumbgate ci-gha-buildkite-patterns --json --workflow=.github/workflows/ci.yml
npx thumbgate ci-gha-buildkite-patterns --json --jobs-json=jobs.json
npm run test:ci-gha-buildkite-patterns
  1. Name first_fail.step before opening logs.
  2. Absent required contexts → githubstatus.com, not a code blame.
  3. E2E shards stay fail-fast: false so merge-reports can still annotate (Buildkite wait + continue_on_failure).
  4. Do not vendor buildkite-agent.

Rubric

  • --map-only → ok=true
  • --clone-buildkite / --migrate / --quarantine / --rerun-queued → fail
  • live ci.yml concurrency excludes main
  • doctor tests PASS
  • evidence: --json in the same turn

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.