errors
Skill1 starsChanged 6 days agoMITView on GitHub
Use when writing or reviewing error handling, validation, exceptions, try/catch, Result types or user-facing error messages, in any language. Keeps failures loud, narrow and honest instead of swallowed or hidden.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- aihu-project/aihutheir own version, first seen Oct 20, 2026
- ayrshare/ayrshare-social-media-api-claude-plugintheir own version, first seen Oct 13, 2026
- mr-ske1r/1c-ai-devstarttheir own version, first seen Oct 13, 2026
- VectorLabAU/skillstheir own version, first seen Oct 11, 2026
- LedgerHQ/ledger-livetheir own version, first seen Oct 8, 2026
- gabriellst/codmtheir own version, first seen Aug 26, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- LedgerHQ/ledger-live★ 627same name
- ayrshare/ayrshare-social-media-api-claude-plugin★ 19same name
- mr-ske1r/1c-ai-devstart★ 16same name
- aihu-project/aihu★ 4same name
- gabriellst/codm★ 4same name
- VectorLabAU/skills★ 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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
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 10
Never swallow errors: no empty catch, no catch-log-continue where the caller needs to know.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Error handling
- Never swallow errors: no empty catch, no catch-log-continue where the caller needs to know. Handle meaningfully or propagate.
- Catch the narrowest type, at the level that can act on it.
- Validate at system boundaries (handlers, CLI args, file and network input); trust internal calls. No handling for cases that cannot happen.
- Fail early with a message naming what went wrong and the value involved. No silent fallbacks that mask bugs.
- User-facing errors say what to do next and never leak internals.
- Release resources on every path (
use, try-with-resources,finally,defer).
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.