ci-pulse
Skill11 starsChanged 50 days agoMITView on GitHub
Collect CI Steward's pipeline numbers right now, locally, into a temporary directory, and show the ci-status screen from them, including this clone's local hook timings. Pushes nothing. Use when the daily snapshot is too old to answer the question.
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-quarantineSkill
- ci-statusSkill
- 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
Files
/ci-pulse
The daily collector runs at 05:00 UTC. A pulse answers "what does it look like now" without waiting for it: the same collect the workflow runs, over yesterday (when the data branch lacks it) and today so far, plus this clone's local hook timings.
Steps
Run it:
pnpm ci:pulseIt seeds a temporary directory from
origin/ci-steward-datawhen that exists (rungit fetch origin ci-steward-datafirst for the latest), collects through yourghlogin, computes verdicts, and prints the/ci-statusscreen. Add--keepto keep the directory and read the raw snapshot.- Relay it the way
/ci-statusdoes: health, the constraint, then notable verdicts.
What it costs and what it never does
- It spends your own GitHub API allowance (5,000 requests an hour for a personal login): about 40 requests on a quiet day, a few hundred on a busy one, capped by
collect.api_budgetinci/config.yaml. - Today is a partial day, so its numbers move until midnight UTC.
- It never pushes to
ci-steward-data, never creates it, and never writes a verdict anywhere but the temporary directory.
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.

