error-paths
Skill0 starsChanged 15 days agoNo licenceView on GitHub
Walk the failure modes of a feature, decide what should happen in each, prove gaps with tests and fix them. Maps the operation from its entry points to every external interaction (HTTP, SDKs, database, queues, files, subprocesses, parsing, auth, clocks, caches, locks, input) and builds a matrix of failure point by failure - timeouts, 4xx and 5xx, bad responses, partial failure, duplicates, races, crashes, out-of-order events, exhaustion, hostile input, time zones, cancellation, wrong data - with current behavior traced from the code, expected behavior from docs, conventions or the user, and a verdict. Verifies every gap, writes a test that must fail first, applies the approved fix and reverts what breaks. Use when the user asks about error handling, failure modes, unhappy paths or resilience of a feature, endpoint, command or job, asks what happens when something fails, or invokes /error-paths (options --report-only, --auto, --failures, --models). Never applies a fix without a per-item yes. Commits nothing.
In this repository12 other files it gives its agents.
- conventionsSkill
- deep-reviewSkill
- dep-hygieneSkill
- deslopSkill
- guided-reviewSkill
- hotspotsSkill
- perf-passSkill
- pr-reviewSkill
- sdlc-fast-piSkill
- sdlc-fastSkill
- sdlc-loopSkill
- test-strengthSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.