ci-failure-triage
Skill0 starsChanged 4 months agoMITView on GitHub
Use when `make ci-local` fails locally or a GitHub Actions run reports a CI failure (format, lint, line-budget, typecheck, or test errors).
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
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 12
Run make ci-local and read the log to see which sub-target failed.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CI Failure Triage
Follow AGENTS.md first.
Workflow
- Run
make ci-localand read the log to see which sub-target failed. It typically chainsformat-check lint-ci lint-loc typecheck test-fast test-integration, but repos vary (e.g.clinvar-linkhas nolint-loc) — trust the actual recipe/CI log, not this list. - Format (
format-check) — runmake format, re-check. - Lint (
lint-ci) — runmake lint-fix; fix remaining findings by hand rather than blanket-ignoring. - Line budget (
lint-loc, the per-file line budget inscripts/check_file_size.py, where present) — split the growing module along its seams; edit.loc-allowlistonly with a tracked decomposition reason. - Typecheck (
typecheck) — runmake typecheck; fix the type, don't add broadignore_errors/# type: ignore. - Tests (
test-fast/test-integration) — fix code or test per the assertion; parser/data changes need fixture-backed coverage undertests/. - Re-run
make ci-localuntil green before handoff.
Common mistakes
- Silencing lint/typecheck instead of fixing the cause.
- Bumping
.loc-allowlistto dodge a needed split. - Committing with a red
ci-local.
Other versions18 projects use a version of this.
Word for word · 8
- berntpopp/genefoundry-router★ 6100% same
- berntpopp/hpo-link★ 1100% same
- berntpopp/mgi-link★ 1100% same
- berntpopp/stringdb-link★ 1100% same
- berntpopp/gnomad-link★ 0100% same
- berntpopp/hgnc-link★ 0100% same
- berntpopp/mondo-link★ 0100% same
- berntpopp/vep-link★ 0100% same
Edited · 0
None found.
Wrote their own version · 10
- MarketSquare/robotframework-browser★ 659same name
- n1m21n/Infinite★ 281same name
- proflead/codex-skills-library★ 153same name
- kaeawc/auto-mobile★ 52same name
- IgorGanapolsky/ThumbGate★ 29same name
- OpenSelfHosting/skills★ 2same name
- skwashd/skills★ 2same name
- berntpopp/gencc-link★ 0same name
- berntpopp/gtex-link★ 0same name
- berntpopp/spliceailookup-link★ 0same name
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
- code-quality-reviewSkill
- dependency-cve-sweepSkill
- fastapi-route-changeSkill
- fleet-standard-adoptionSkill
- mcp-tool-changeSkill
- release-readinessSkill
- security-reviewSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.