loop-triage-ci
Skill3 starsChanged 10 months agoMITView on GitHub
Use for an Engram CI sweeper triage loop that groups CI failures, classifies root causes, caps attempts, and proposes bounded minimal-fix candidates only after budget, denylist, and verifier gates.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- aiconnai/agentshieldedited, first seen Jun 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- aiconnai/agentshield★ 2193% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agentshield-scanSkill
- dependency-triageSkill
- engram-councilSkill
- engram-onboardingSkill
- loop-engineeringSkill
- loop-triageSkill
- pr-review-triageSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill to identify repeated or impactful CI failures and classify bounded automated-fix candidates.
- Distinctive: line 15
Commit that introduced failures, when available.
- Distinctive: line 22
Write only actionable findings:
- Distinctive: line 51
Prefer the smallest diff that addresses the failing check.
- Distinctive: line 52
Do not auto-fix dependency-major upgrades, auth, storage migrations, attestation/snapshot code, release publishing, production …
≈ “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
CI Sweeper Triage Loop
Use this skill to identify repeated or impactful CI failures and classify
bounded automated-fix candidates. Pair it with
skills/loop-engineering/SKILL.md for global loop safety rules.
Inputs
- Failed checks list with messages and logs.
- Commit that introduced failures, when available.
- Retry count and history from prior runs.
- Current
ci-sweeper-state.md,loop-run-log.md, andloop-budget.md. - Current denylist, allowlist, and pause flags.
Output
Write only actionable findings:
## High Priority
- Check:
Root cause class: lint | test | type | runtime | dependency | config
Repro confidence: high | medium | low
Minimal fix path:
Attempt:
## Watch
## Escalate
- Flakes:
- Infra/noise:
- Repeated failures with no stable fix:
## Suggested Loop Action
- open worktree + minimal-fix
- ESCALATE_HUMANAppend a short run summary to ci-sweeper-state.md and one JSON line or table
row to loop-run-log.md, matching the repository's existing loop-log format.
Rules
- Cap attempts at 3 per item.
- Reproduce or identify the failure class before proposing a fix.
- Prefer the smallest diff that addresses the failing check.
- Do not auto-fix dependency-major upgrades, auth, storage migrations, attestation/snapshot code, release publishing, production infrastructure, or other denylisted paths.
- Route flakes, infrastructure failures, repeated low-confidence failures, and
exhausted attempts to
ESCALATE_HUMAN. - For low-risk candidates, create an isolated worktree and dispatch a
minimal-fiximplementer followed by an independent verifier.
Verification Gate
The verifier must check:
- The original failing command or closest local equivalent.
- Relevant tests, lint, type checks, or build commands.
- Scope diff against the declared minimal fix path.
- The full Engram gate when agent, script, CI, connector, dependency, or policy
surfaces changed:
bash docs/harness/bin/sensors.sh. - The denylist before any PR, merge, or external write.
Completion Gate
Mark the run complete only when the state files include the attempt count, confidence, evidence, next action, and clear escalation for denied or uncertain items.
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.

