build-rescue
Skill0 starsChanged 13 days agoMITView on GitHub
Investigate and repair a failing build or CI job from logs to a verified fix. Use when compilers, linters, tests, containers, or CI workflows break.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ditomax/buildtheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ditomax/build★ 1same 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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-skill-auditSkill
- api-contract-checkSkill
- change-narrativeSkill
- context-handoffSkill
- data-quality-gateSkill
- dataset-workshopSkill
- dependency-careSkill
- docs-syncSkill
- experiment-ledgerSkill
- failure-forensicsSkill
- model-diff-reviewSkill
- model-eval-designSkill
- multi-agent-crosscheckSkill
- parallel-task-designSkill
- performance-proofSkill
- release-readinessSkill
- repo-scoutSkill
- research-evidence-mapSkill
- review-lensSkill
- safe-migrationSkill
- security-surfaceSkill
- spec-firstSkill
- sql-integrity-checkSkill
- test-driven-changeSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 22
Do not print CI secrets or include tokens in logs.
- Distinctive: line 23
Do not rerun a workflow that deploys, publishes, charges, or mutates production unless authorized.
- Distinctive: line 24
Never mark a failure resolved just because a retry passed once.
≈ “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
Build Rescue
Procedure
- Capture the exact failing command, exit code, full relevant log context, commit, OS/runtime, and dependency lock state.
- Determine whether the failure is deterministic, environment-only, network-related, flaky, or introduced by a code change.
- Reproduce locally or in the closest equivalent environment. If reproduction differs, document the gap.
- Locate the earliest meaningful error, not just the final cascade. Check configuration, version drift, missing artifacts, permissions, and concurrency assumptions.
- Change one cause at a time. Avoid bypassing the build step, suppressing diagnostics, disabling tests, or weakening type/lint checks without a justified migration plan.
- Rerun the failing job, then the relevant broader checks. For flaky failures, repeat enough times to test the hypothesis and report the repeat count.
- Inspect workflow changes for secret exposure, unsafe permissions, unpinned actions, cache poisoning, and accidental release/deploy triggers.
Deliverable
Root cause, minimal repair, exact successful commands or CI run IDs, checks not run, and any environment-specific caveats.
Boundaries
- Do not print CI secrets or include tokens in logs.
- Do not rerun a workflow that deploys, publishes, charges, or mutates production unless authorized.
- Never mark a failure resolved just because a retry passed once; assess flaky behavior honestly.
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.