agentleFS
y-miyazakiy-miyazaki/config/.agents/skills/ci-sweeper/SKILL.md

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.

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

    When intent is unclear, survey and offer to apply — edits are harder to undo than a report.

    line 66
  2. Very specific:

    When agent_edit_allowed is true, resolve agent_edit_target: on the interactive path use fix (this skill).

    line 68
  3. Very specific:

    IF detect reports skip OR no actionable failures after gathering → emit survey no-op per common-output-format.md (Overview explains no-op).

    line 72
  4. Very specific:

    IF agent_edit_allowed is false → emit survey shape (### Candidates for regressions, ### Watch for Watch-class failures).

    line 74
  5. Very specific:

    After edits, run the repository's existing check for each fixed job (the command the failing job runs, when available locally) and record …

    line 78

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

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

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 ## Constraints or 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_allowed and agent_edit_target from ## Constraints per 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.md and assets/pr-body-template-survey.md (read when synthesizing the PR body)

Workflow

Resolve agent_edit_allowed before classifying failures:

Sourceagent_edit_allowed
Interactive — default: the request asks to look, check, triage, or survey, or only names the skillfalse — 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 applytrue
Automation — ## Constraintsagent_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.

  1. 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 (default all), 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.
  2. On the automation path, read category-automation-envelope.md for Constraints, PR templates, and Session Metrics.
  3. IF detect reports skip OR no actionable failures after gathering → emit survey no-op per common-output-format.md (Overview explains no-op); on automation path append ## Session Metrics per category-automation-envelope.md; stop.
  4. Classify each failure per common-checklist.md: fixable regression within scope, or Watch-class (flake, infra, env, or a fix requiring more than five files). Note ignored[] in Overview when non-empty.
  5. IF agent_edit_allowed is false → emit survey shape (### Candidates for regressions, ### Watch for Watch-class failures); on automation path load assets/pr-body-template-survey.md at synthesis and append ## Session Metrics per category-automation-envelope.md; stop — do not edit files.
  6. ELSE IF agent_edit_allowed is true AND agent_edit_target is not fix → emit survey shape; note expected agent_edit_target: fix in Overview; stop — do not edit files.
  7. ELSE IF no failure is a fixable regression (every failure is Watch-class) → emit survey shape with ### Watch per common-output-format.md; on automation path load assets/pr-body-template-survey.md at synthesis and append ## Session Metrics per category-automation-envelope.md; stop — do not edit files.
  8. ELSE (agent_edit_allowed is true AND agent_edit_target is fix) → 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.
  9. 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.
  10. Emit apply shape per common-output-format.md: fixed regressions under ### Changes; deferred regressions and Watch-class failures under ### Deferred. Reconcile Changes / Deferred with git diff --name-only; on automation path load assets/pr-body-template.md at synthesis and append ## Session Metrics (including validation commands) per category-automation-envelope.md.

Error Handling

ConditionSeverityAction
Detect script non-zero exit or status: "error" (when invoked)FatalRead stdout; stop — do not treat as success-path detect JSON
skip or no actionable failuresInfoEmit survey no-op (Overview explains no-op); stop
Edit requested but ## Constraints set agent_edit_allowed: falseInfoSurvey only; note that the caller Constraints disallow edits
agent_edit_allowed true with agent_edit_target not fixRecoverableSurvey only; note expected agent_edit_target: fix
A failure is infra/env/flake or needs >5 filesRecoverableNo edits for that failure; Watch (survey) or Deferred (apply); continue with the others
Validation tooling missingRecoverableDefer the failure unless fixing one line from log_excerpt
Path outside allowlistRecoverableWatch 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_allowed is true and agent_edit_target is fix.

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.