error-handling-resilience
Skill15 starsChanged 5 months agoCC0-1.0View on GitHub
Performs a comprehensive error-handling review across the codebase, checking coverage, propagation, and recovery. Use when auditing how the system handles and recovers from failures.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 14
If no target path is given above, review the entire codebase.
- Distinctive: line 70
Prefer minimal, drop-in fix snippets over prose.
- Distinctive: line 72
Do not invent files or functions that aren’t present.
- Distinctive: line 74
Write this into a markdown file and place it in the audits/ folder.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Target: $ARGUMENTS
If no target path is given above, review the entire codebase.
Evaluate this entire software package.
Perform a comprehensive error handling review:
Evaluate:
- ERROR HANDLING CONSISTENCY
- Is there a centralized error handler?
- Are errors handled uniformly?
- Custom error classes vs generic errors?
- ERROR CATEGORIES
- Validation errors (400)
- Authentication errors (401)
- Authorization errors (403)
- Not found errors (404)
- Server errors (500)
- Rate limit errors (429)
- Are they properly categorized?
- ASYNC ERROR HANDLING
- Unhandled promise rejections
- Async middleware wrapper usage
- Callback error handling
- Event emitter error handling
- ERROR RECOVERY
- Graceful degradation
- Retry mechanisms
- Circuit breakers
- Fallback strategies
- ERROR INFORMATION
- Development vs production error details
- Stack trace exposure
- Error logging completeness
- User-friendly error messages
Identify error handling gaps and provide improved implementation.
Provide:
A structured finding report
A scale of 1/10 on how important each finding is
Remediation: precise code-level fix or config change (snippets welcome) if possible
Constraints & style:
Be concrete and cite exact code locations and identifiers.
Prefer minimal, drop-in fix snippets over prose.
Do not invent files or functions that aren’t present; if context is missing, mark as Unable to verify and say what code would prove it.
Write this into a markdown file and place it in the audits/ folder.
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- mmondora/claude-skills★ 1same name
- novatic-cu/nova-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.
In this repository21 other files it gives its agents.
- api-and-infrastructureSkill
- authentication-flow-reviewSkill
- authorization-implementationSkill
- business-logic-vulnerabilitiesSkill
- code-duplication-detectionSkill
- code-quality-metrics-standardsSkill
- comprehensive-security-reportSkill
- database-securitySkill
- design-pattern-implementationSkill
- exception-flow-analysisSkill
- file-handling-business-logicSkill
- initial-security-analysisSkill
- initial-software-design-analysisSkill
- input-validationSkill
- logging-monitoringSkill
- readability-and-namingSkill
- resilience-fault-toleranceSkill
- secrets-management-auditSkill
- session-cookie-securitySkill
- solid-principlesSkill
- testing-implementationSkill
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.