sweep-ci
Skill14 starsChanged 3 months agoMITView on GitHub
Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Sweep CI”. A useful skill states the six fields from Skills and routines. CI on named repositories is red or flaky and the owner needs a failure list with logs and owners — not a bot that reruns, cancels, or merges. Every row cites a check URL or log line. Flakes are labeled when the same job failed then passed without…
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- convert/claude.mdCLAUDE.md
- docs/llms.txtllms.txt
- audit-subscriptionsSkill
- cited-researchSkill
- cloud-bill-noteSkill
- collate-feature-asksSkill
- coordinate-launchSkill
- daily-digestSkill
- defend-calendarSkill
- design-bot-templateSkill
- detect-docs-driftSkill
- diff-competitorsSkill
- draft-call-followupSkill
- draft-changelogSkill
- draft-issueSkill
- draft-newsletterSkill
- draft-security-answersSkill
- draft-sqlSkill
- draft-support-replySkill
- garden-memorySkill
- harden-repoSkill
- incident-timelineSkill
- install-teamSkill
- interrogate-assumptionsSkill
- investigate-perfSkill
- log-promisesSkill
- package-evidenceSkill
- plan-tripSkill
- prep-meetingSkill
- queue-socialSkill
- ramp-new-hireSkill
- rank-account-healthSkill
- recommend-media-reallocSkill
- reconcile-expensesSkill
- remix-contentSkill
- reproduce-bugSkill
- research-accountsSkill
- review-pr-riskSkill
- route-workSkill
- sanitize-shareSkill
- scout-x-threadsSkill
- source-talentSkill
- triage-inboxSkill
- vendor-renewalsSkill
- watch-aeoSkill
- watch-brandSkill
- weekly-saas-financeSkill
- write-win-lossSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- could be automatic: a setting could enforce it
- Distinctive: line 17
Default branch and the time window (default since last sweep)
- Distinctive: line 27
Write the sweep memo. Do not cancel runs, push, merge, or mute required checks.
- Distinctive: line 31
Every row cites a check URL or log line.
- Distinctive: line 41
Do not merge, push, or comment on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Sweep CI
Paste this into Grok Bot after a successful run:
Save the process we just used as a skill called “Sweep CI”.
A useful skill states the six fields from Skills and routines.
1. When to use it
CI on named repositories is red or flaky and the owner needs a failure list with logs and owners — not a bot that reruns, cancels, or merges.
2. Required inputs and access
- GitHub connector and the named repositories
- Default branch and the time window (default since last sweep)
- Optional CODEOWNERS or a pinned owner map
3. Sequence of work
- List failing or cancelled checks on the default branch and on open PRs in the window. Do not invent jobs.
- Open the log for each distinct failure. Quote the error, path, and job name.
- Cluster duplicates. Count how often the same test failed.
- Suggest an owner from CODEOWNERS or the PR author. Do not assign on GitHub.
- At most one rerun, and only when the log is truncated — write that down. Never rerun-until-green.
- Write the sweep memo. Do not cancel runs, push, merge, or mute required checks.
4. How to validate the result
Every row cites a check URL or log line. Flakes are labeled when the same job failed then passed without a code change; otherwise "flake unknown". No merge and no retry loop.
5. What to return
CI sweep: failing jobs, cluster, log quote, suggested owner, flake note, action log. At most one truncated-log rerun recorded.
6. What requires approval
Do not merge, push, or comment on GitHub. Do not cancel workflows or change branch protection. Do not rerun until green.
Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.
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.