explain-error

Solid

Use when a stack trace, exception, or failing build appears and you need the root cause and a concrete fix, not a guess.

AI & Automation 1 stars 0 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
10
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
37
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Explain Error ## When to use Use this skill whenever a test, build, or runtime failure needs diagnosis before you change anything. ## Steps 1. Read the full error and the referenced file:line; don't stop at the last line. 2. Reproduce minimally if the cause is unclear. 3. Identify the root cause: type mismatch, None, version drift, config, race. 4. Propose the smallest correct fix and explain why it resolves the cause. 5. Suggest a guard (test, assertion, type) so it does not recur silently. ## Examples - "Why is this TypeError thrown here?" - "Explain this CI failure and how to fix it" ## References Distinguish the symptom from the cause; fix the cause, and add a regression test so the same error is caught next time.

Details

Author
NSBen
Repository
NSBen/skillfoundry
Created
4 days ago
Last Updated
4 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category