repair-and-resume
Skill2 starsChanged 4 days agoApache-2.0View on GitHub
Repair ordinary failures and continue the original task instead of creating recovery bureaucracy.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-orchestrationSkill
- change-aware-verificationSkill
- context-continuitySkill
- execution-intent-preservationSkill
- independent-engineering-reviewSkill
- observable-progressSkill
- outcome-driven-engineeringSkill
- prototype-firstSkill
- source-custodySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 11
Check actual GitHub/process state before duplicating an uncertain side effect.
- Distinctive: line 12
Avoid broad reruns, speculative defensive layers and endless restart campaigns.
≈ “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
Repair and Resume
- Preserve actual work and inspect the failure before repeating anything.
- Reproduce, fix and validate ordinary bugs; resume the original objective.
- Distinguish safely retryable failures from uncertain external GitHub writes or model outcomes.
- Check actual GitHub/process state before duplicating an uncertain side effect.
- Avoid broad reruns, speculative defensive layers and endless restart campaigns.
- Return the repaired artifact and remaining real blockers, not just a passing diagnostics report.
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.