depot-ci
Skill927 starsChanged 13 days agoMITView on GitHub
Modify Base Depot CI workflows, especially PR cost controls, path filters, runner sizing, or optional integration checks.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
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
- Very specific: line 8
Use the workflows in .depot/workflows/ for Depot CI changes.
- Distinctive: line 10
Treat path filters as a risk boundary: include shared workspace, lockfile, toolchain, setup-action, and workflow inputs when they can …
- Distinctive: line 11
Do not make a required check disappear at workflow dispatch time without confirming branch-protection behavior.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Depot CI
Use the workflows in .depot/workflows/ for Depot CI changes. Keep normal PR feedback focused on checks relevant to the changed subsystem, while preserving exhaustive validation in ci-merge-queue.yml.
- Treat path filters as a risk boundary: include shared workspace, lockfile, toolchain, setup-action, and workflow inputs when they can affect a suite. Prefer running an unnecessary job to omitting relevant coverage.
- Do not make a required check disappear at workflow dispatch time without confirming branch-protection behavior. Prefer a stable workflow with a skipped job, and preserve manual dispatch or a reviewer-label escape hatch for optional work.
ci:system,ci:base-std, andci:perfopt a PR into the corresponding expensive suite;ci:fullopts into all of them. Merge-queue runs are intentionally unconditional.- Measure a proposal using runner-size-weighted duration and report the affected suites. Depot billing and wall-clock latency are separate metrics.
Other versions4 projects use a version of this.
Word for word · 1
- base/base★ 927100% same
Edited · 0
None found.
Wrote their own version · 3
- PostHog/posthog★ 40ksame name
- PostHog/posthog-foss★ 727same name
- depot/skills★ 2same 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 repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- verify-baseSkill
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.