Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jnmetacode/systematic-debugging
Root-cause a bug with a hypothesis-driven loop instead of shotgun edits.
Passed 20 of 23 test cases with the skill, and 15 of 23 without it.
and 4 more in the full report
5 fixed15 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am debugging an intermittent API 500 error in our Node.js microservice. I have already applied 3 different fixes to the controller and database layer, but none of them solved the problem. What should my next step be? Should I attempt a 4th fix by rewriting the query builder logic?
| Checked | Without skill | With skill |
|---|---|---|
| The response instructs to stop attempting further code fixes. | Passed | Passed |
| The response directs to discuss or re-evaluate the system architecture before making any new fix attempt. | Missed | Passed |
The instructions your model reads when the skill loads.
核心原则: 在尝试修复之前,务必先找到根本原因。只修症状就是失败。
敷衍走流程等于违背调试的精神。
不做根因调查,不许提修复方案
如果你还没完成第一阶段,就不能提出修复方案。
用于任何技术问题:
尤其在以下情况必须使用:
以下情况也不要跳过:
test cases passed, vs 15 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.