read-the-trace
starsforks
How to install read-the-trace?
archive228/loopkit/read-the-trace
$npx -y skills add Archive228/loopkit --skill read-the-traceExtract the actual cause from a stack trace instead of pattern-matching the error type. Use on any crash or exception.
SKILL.md
| 1 | # Read the Trace |
| 2 | LLMs love to see "TypeError" and generate a generic fix without reading the trace. Don't. |
| 3 | - Find the **deepest frame in YOUR code** — not the library frame at the top. That's where the bad value entered. |
| 4 | - Read the actual values: what was null/undefined/wrong-type, and where it came from. |
| 5 | - Trace it one level up: why was that value bad? The root is usually 1-2 frames above the throw. |
| 6 | - Reproduce with that exact input before fixing. |
| 7 | A TypeError can mean a hundred things. The trace tells you which one — read all of it, including the "caused by". |
People who liked this also viewed
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training SkillsMay 2026
- explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026
- minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026
- insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 2026
