agentleFS
dork-labsdork-labs/dorkos/.agents/skills/ci-status/SKILL.md

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

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
  1. Distinctive:

    If the person wants the picture rather than the numbers, build the day's page and open it:

    line 29

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/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

  1. 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 || true
  2. Show the screen:

    pnpm ci:status

    It reads origin/ci-steward-data through git objects only. When the branch does not exist yet, it says so plainly and points at pnpm ci:pulse.

  3. Relay it briefly: health first (anything FAILED or a snapshot over 2 days old is the headline), then the constraint, then any red trigger, then any verdict that is failed, partial or inconclusive. Do not restate the whole table.
  4. If the person wants the picture rather than the numbers, build the day's page and open it:

    pnpm ci:report --open

    It 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. red means act; amber means decide. Each says how long it has been open and whether a proposed ledger 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 (or pnpm ci:report); the Monday deep summary is :reports/<YYYY-Www>.md.

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.