ci-status
Skill11 starsChanged 50 days agoMITView on GitHub
Show CI Steward's one-screen view of the pipeline: the SLO table, the one constraint to work on, the open improvement triggers, every ledger experiment with its computed verdict, and the collector's health. Reads the ci-steward-data branch; run it before changing CI or when asked how CI is doing.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- dotnet/androidtheir own version, first seen Oct 8, 2026
- DenisovAV/flutter_gemmatheir own version, first seen Oct 8, 2026
- mono/SkiaSharptheir own version, first seen Oct 8, 2026
- mifunedev/skillstheir own version, first seen Oct 3, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- mono/SkiaSharp★ 5.6ksame name
- dotnet/android★ 2.1ksame name
- DenisovAV/flutter_gemma★ 654same name
- mifunedev/skills★ 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 repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- auditing-uiSkill
- browser-testingSkill
- capturing-product-mediaSkill
- ci-local-exportSkill
- ci-pulseSkill
- ci-quarantineSkill
- creating-pull-requestsSkill
- debugging-systematicallySkill
- debugging-test-failuresSkill
- debugging-typescript-errorsSkill
- deps-weeklySkill
- designing-frontendSkill
- opensrcSkill
- organizing-fsd-architectureSkill
- runtime-watchSkill
- stewarding-ci-pipelineSkill
- syncing-agent-skillsSkill
- verification-before-completionSkill
- vision-drift-checkSkill
- visual-companionSkill
- writing-adrsSkill
- writing-app-copySkill
- writing-blog-postsSkill
- writing-changelogsSkill
- writing-developer-guidesSkill
- writing-for-humansSkill
- writing-to-usersSkill
- adding-config-fieldsSkill
- clarifying-requirementsSkill
- maintaining-dependenciesSkill
- maintaining-dev-playgroundSkill
- managing-specsSkill
- marketplace-devSkill
- orchestrating-parallel-workSkill
- reading-session-transcriptsSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- styling-with-tailwind-shadcnSkill
- test-driven-developmentSkill
- upgrading-runtime-dependenciesSkill
- working-in-worktreesSkill
- dorkbot-triageSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
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 29
If the person wants the picture rather than the numbers, build the day's page and open it:
“Common” is measured: kept by at least 6 in 10 of the 4 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
/ci-status
The first stop before any pipeline change (contributing/ci.md). It joins the ledger on this checkout (ci/ledger/) with what the daily collector computed on the ci-steward-data branch.
Steps
Bring the data branch up to date. This is the only network step, and a failure is fine (the branch may not exist yet):
git fetch --quiet origin ci-steward-data || trueShow the screen:
pnpm ci:statusIt reads
origin/ci-steward-datathrough git objects only. When the branch does not exist yet, it says so plainly and points atpnpm ci:pulse.- Relay it briefly: health first (anything
FAILEDor a snapshot over 2 days old is the headline), then the constraint, then any red trigger, then any verdict that isfailed,partialorinconclusive. Do not restate the whole table. If the person wants the picture rather than the numbers, build the day's page and open it:
pnpm ci:report --openIt writes to a temp path, never to the data branch, and never pushes.
Reading it
- Health FAILED means the collector's own numbers cannot be trusted (a truncated fetch, a drifted ruleset, a missing data-branch safeguard, no clone exporting local timings for 3 days). Each failure line names its fix. It is the constraint until it is fixed.
- insufficient is a thin sample, not a breach or a win. unmeasured means the SLO has no data source yet.
- Verdicts are computed by code, never written by hand:
verified(reached the target),partial(at least halfway from the baseline, short of the target),failed,inconclusive(a confounding change on the same gate, or too little data),pending(the after-window is still open). - Triggers are computed from the data, not written by a model: what fired, with its numbers, and a suggested next step.
redmeans act;ambermeans decide. Each says how long it has been open and whether aproposedledger entry already covers it. A trigger opens no pull request and changes nothing by itself. - The day's report is
git show origin/ci-steward-data:reports/<YYYY-MM-DD>.html(orpnpm ci:report); the Monday deep summary is:reports/<YYYY-Www>.md.
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.

