read-the-trace
Extract the actual cause from a stack trace instead of pattern-matching the error type. Use on any crash or exception.
来源信息
- 仓库
- Archive228/loopkit
- 最近来源活动
- 2026年6月29日 22:25
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 757
- Forks
- 124
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- read-the-trace
- description
- Extract the actual cause from a stack trace instead of pattern-matching the error type. Use on any crash or exception.
- when_to_use
- a stack trace, an exception, "TypeError/NullPointer/undefined", a crash log
# Read the Trace
LLMs love to see "TypeError" and generate a generic fix without reading the trace. Don't.
- Find the **deepest frame in YOUR code** — not the library frame at the top. That's where the bad value entered.
- Read the actual values: what was null/undefined/wrong-type, and where it came from.
- Trace it one level up: why was that value bad? The root is usually 1-2 frames above the throw.
- Reproduce with that exact input before fixing.
A TypeError can mean a hundred things. The trace tells you which one — read all of it, including the "caused by".
在 GitHub 查看