agentleFS
davidvornholtdavidvornholt/mailbox/.agents/skills/ci-pipelines/SKILL.md

ci-pipelines

Skill2 starsChanged 10 days agoMITView on GitHub

Use when changing continuous integration, GitHub Actions workflows, runners, caches, or deployment pipelines. Keeps CI fail-closed.

3 other projects use a version of this.

Adopted by

Most recently taken up by

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:

    Leave package and browser stores at their tools' default paths.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 pipelines

CI fails closed. A step that can't establish what it relies on, such as a diff, a signature, or a gate result, takes the full path or fails the run.

Reference external actions by their major-version tag, such as actions/checkout@v7, not by commit SHA. The owner accepts the risk that a tag is retargeted, so don't propose SHA pins.

Each job bills at least one minute, so fold sub-minute checks into an existing job that runs at the same trust level.

GitHub behavior

A workflow-level paths filter can't prove that a gate has nothing to check, because GitHub evaluates it against a bounded list of changed files. Classify the checked-out diff in a job instead.

GitHub counts a skipped job as a passing required check. On runs that skip a gate, the job that reports its required check needs another name.

Caches

Save caches only from successful default-branch runs. Other runs only restore them.

Leave package and browser stores at their tools' default paths. Turbo's strict environment hides the variables that relocate a store from the tools a task spawns.

Never cache image layers with type=gha, because their churn in the shared Actions cache quota costs more than the cache saves. Cache them in the image's registry instead, as type=registry,ref=ghcr.io/<owner>/<image>:buildcache. Every build reads it, and only default-branch push builds write it, with mode=max,image-manifest=true,oci-mediatypes=true. Registry retention must keep the :buildcache tag.

Deployment

Deploy a commit only after the quality gate passed for that exact commit. Serialize deployments with FIFO queueing (concurrency.queue: max), because otherwise a late run for an older commit can evict the pending run for the newest one.

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.