ci-sweeper
Skill1 starsChanged 10 days agoApache-2.0View on GitHub
Triage failing CI on integration branches and/or PR heads, classify failures, apply minimal fixes when actionable. Use in conversation when the user asks to triage or fix CI failures. Also the loop entry skill when automation detects failed workflow runs or supplies detection JSON. Interactive default is survey only; edit files when the request asks for changes to be made (for example fix, apply, or update) or automation sets agent_edit_allowed in Constraints.
In this repository56 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .apm/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/workflows/CLAUDE.mdCLAUDE.md
- .cursor/rules/agent-skills.mdcCursor rule
- .cursor/rules/bats.mdcCursor rule
- .cursor/rules/github-actions-workflow.mdcCursor rule
- .cursor/rules/go.mdcCursor rule
- .cursor/rules/go-test.mdcCursor rule
- .cursor/rules/instructions.mdcCursor rule
- .cursor/rules/markdown.mdcCursor rule
- .cursor/rules/shell-script.mdcCursor rule
- .cursor/rules/terraform.mdcCursor rule
- agent-skills-reviewSkill
- changelogSkill
- docs-creatorSkill
- docs-updaterSkill
- github-actions-reviewSkill
- github-actions-validationSkill
- github-issue-autofixSkill
- github-issue-triageSkill
- github-pr-bodySkill
- github-pr-reviewSkill
- github-pr-reviseSkill
- go-reviewSkill
- go-validationSkill
- instructions-reviewSkill
- loop-verifierSkill
- markdown-validationSkill
- refactorSkill
- shell-script-reviewSkill
- shell-script-validationSkill
- tech-debtSkill
- test-gapSkill
- agent-skills-reviewSkill
- changelogSkill
- ci-sweeperSkill
- docs-creatorSkill
- docs-updaterSkill
- github-actions-reviewSkill
- github-actions-validationSkill
- github-issue-autofixSkill
- github-issue-triageSkill
- github-pr-bodySkill
- github-pr-reviewSkill
- github-pr-reviseSkill
- go-reviewSkill
- go-validationSkill
- instructions-reviewSkill
- loop-verifierSkill
- markdown-validationSkill
- refactorSkill
- shell-script-reviewSkill
- shell-script-validationSkill
- tech-debtSkill
- test-gapSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 66
When intent is unclear, survey and offer to apply — edits are harder to undo than a report.
- Very specific: line 68
When agent_edit_allowed is true, resolve agent_edit_target: on the interactive path use fix (this skill).
- Very specific: line 72
IF detect reports skip OR no actionable failures after gathering → emit survey no-op per common-output-format.md (Overview explains no-op).
- Very specific: line 74
IF agent_edit_allowed is false → emit survey shape (### Candidates for regressions, ### Watch for Watch-class failures).
- Very specific: line 78
After edits, run the repository's existing check for each fixed job (the command the failing job runs, when available locally) and record …
≈ “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
UTILITY SKILL — CI failure triage and minimal fix, not merge or release.
Input
- Interactive (required): natural-language request; optional failure context (URLs, logs, job names) — constraints in
## Constraintsor category-scope.md - Automation (optional): detect JSON in prompt — from a caller or optional skill detect script; not required for interactive runs. Read
agent_edit_allowedandagent_edit_targetfrom## Constraintsper category-automation-envelope.md
Path allowlist, when present, arrives in ## Constraints.
Output Specification
Triage report per common-output-format.md. Survey shape when files are not edited; apply shape when edited — within category-scope.md.
Execution Scope
USE FOR:
- Classify CI failures; apply minimal lint/workflow/shell/doc fixes
DO NOT USE FOR:
- Infra outages, secrets, or runner capacity issues (classify as Watch)
- Refactors >5 files or auth/payment/credential paths
- Merge PRs or push to default branch
Reference Files Guide
- common-checklist.md (always read)
- common-output-format.md (always read)
- category-scope.md (always read)
- category-detect-scope.md (read on interactive path)
- category-input-schema.md (read when detect JSON is present or the optional detect script is run)
- category-run-ledger.md (read when ignored[] is non-empty)
- category-automation-envelope.md (read on automation path)
- common-troubleshooting.md (read on failure)
- category-pr-body-links.md (read when synthesizing the PR body)
assets/pr-body-template.mdandassets/pr-body-template-survey.md(read when synthesizing the PR body)
Workflow
Resolve agent_edit_allowed before classifying failures:
| Source | agent_edit_allowed |
| Interactive — default: the request asks to look, check, triage, or survey, or only names the skill | false — survey only; do not edit files |
| Interactive — the request asks for changes to be made (for example fix, apply, 修正して, 適用して, update, add) | true |
| Interactive — follow-up after a survey asking to apply | true |
Automation — ## Constraints | agent_edit_allowed: true or agent_edit_allowed: false from category-automation-envelope.md |
When intent is unclear, survey and offer to apply — edits are harder to undo than a report.
When agent_edit_allowed is true, resolve agent_edit_target: on the interactive path use fix (this skill); on the automation path read agent_edit_target from ## Constraints. Do not branch on other caller metadata outside ## Constraints.
- Resolve scope (category-scope.md). Parse detect JSON when present; otherwise resolve the detect universe from the prompt (category-detect-scope.md), run this skill's optional detect script with the resolved
--scope(defaultall), then Agent-complement beyond mechanical output; if tools for detect are unavailable, gather failures from the user request and available CI/log context instead of silent no-op. Load category-input-schema.md when parsing detect output. On detect script non-zero exit, read stdout and stop. - On the automation path, read category-automation-envelope.md for Constraints, PR templates, and Session Metrics.
- IF detect reports
skipOR no actionable failures after gathering → emit survey no-op per common-output-format.md (Overview explains no-op); on automation path append## Session Metricsper category-automation-envelope.md; stop. - Classify each failure per common-checklist.md: fixable
regressionwithin scope, or Watch-class (flake,infra,env, or a fix requiring more than five files). Noteignored[]in Overview when non-empty. - IF
agent_edit_allowedisfalse→ emit survey shape (### Candidatesfor regressions,### Watchfor Watch-class failures); on automation path loadassets/pr-body-template-survey.mdat synthesis and append## Session Metricsper category-automation-envelope.md; stop — do not edit files. - ELSE IF
agent_edit_allowedistrueANDagent_edit_targetis notfix→ emit survey shape; note expectedagent_edit_target: fixin Overview; stop — do not edit files. - ELSE IF no failure is a fixable regression (every failure is Watch-class) → emit survey shape with
### Watchper common-output-format.md; on automation path loadassets/pr-body-template-survey.mdat synthesis and append## Session Metricsper category-automation-envelope.md; stop — do not edit files. - ELSE (
agent_edit_allowedistrueANDagent_edit_targetisfix) → fix fixable regressions within category-scope.md. When more than three failures are present, fix only the first regression and defer the rest. Watch-class failures get no edits. - After edits, run the repository's existing check for each fixed job (the command the failing job runs, when available locally) and record commands and outcomes in
## Verification; never claim a check passed when it failed or was not run. - Emit apply shape per common-output-format.md: fixed regressions under
### Changes; deferred regressions and Watch-class failures under### Deferred. Reconcile Changes / Deferred withgit diff --name-only; on automation path loadassets/pr-body-template.mdat synthesis and append## Session Metrics(including validation commands) per category-automation-envelope.md.
Error Handling
| Condition | Severity | Action |
Detect script non-zero exit or status: "error" (when invoked) | Fatal | Read stdout; stop — do not treat as success-path detect JSON |
skip or no actionable failures | Info | Emit survey no-op (Overview explains no-op); stop |
Edit requested but ## Constraints set agent_edit_allowed: false | Info | Survey only; note that the caller Constraints disallow edits |
agent_edit_allowed true with agent_edit_target not fix | Recoverable | Survey only; note expected agent_edit_target: fix |
| A failure is infra/env/flake or needs >5 files | Recoverable | No edits for that failure; Watch (survey) or Deferred (apply); continue with the others |
| Validation tooling missing | Recoverable | Defer the failure unless fixing one line from log_excerpt |
| Path outside allowlist | Recoverable | Watch or defer; do not edit |
Examples
- Prompt:
Triage failing CI on the integration branch - Result: Survey report per references/common-output-format.md; apply one-line regression fixes only when
agent_edit_allowedis true andagent_edit_targetisfix.
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.

