ci-pipelines
Skill2 starsChanged yesterdayMITView on GitHub
Use when changing continuous integration, GitHub Actions workflows, runners, caches, or deployment pipelines.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- davidvornholt/mailboxword for word, first seen Nov 15, 2026
- poorvith-mp/skills-developertheir own version, first seen Aug 19, 2026
Other versions3 projects use a version of this.
Word for word · 1
- davidvornholt/mailbox★ 2100% same
Edited · 0
None found.
Wrote their own version · 2
- lengrufeng2008/dsh-skill-library★ 0same name
- poorvith-mp/skills-developer★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- databaseSkill
- declarative-infraSkill
- frontend-designSkill
- issuesSkill
- nextjsSkill
- prsSkill
- review-fixSkill
- reviewSkill
- screenshots-in-prsSkill
- secrets-and-configSkill
- standards-syncSkill
- ux-uiSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 24
Leave package and browser stores at their tools' default paths.
- Distinctive: line 34
Before a release, the job that builds the app's image starts the container, waits for its health check, sends SIGTERM, and fails unless the …
≈ “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.
Files
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
Release to production only a commit whose exact tree passed the full quality gate. A pull request preview is the exception: it deploys once its image passes the migration and health smoke test, without waiting for the gate, under the protections in Pull request previews. 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.
The gate loads an app's production build in a browser and fails on an uncaught page error, because a server-only module in the browser bundle can leave every page unresponsive while every test passes.
Before a release, the job that builds the app's image starts the container, waits for its health check, sends SIGTERM, and fails unless the app exits as the app-release contract requires, because a shell or runtime running as PID 1 can ignore the signal.
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.

