开发与测试
systematic-debugging
Use to investigate a failure whose cause is unclear, crosses component boundaries, or persists after a previous fix. Straightforward errors with an established cause can be fixed directly.
chipfighter · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add chipfighter/coding-discipline --skill systematic-debugging技能说明
name: systematic-debugging description: Use to investigate a failure whose cause is unclear, crosses component boundaries, or persists after a previous fix. Straightforward errors with an established cause can be fixed directly. license: MIT
- Capture the failing behavior with a small reproduction. If it is intermittent or unavailable, use logs, traces, or a comparison with a known-good run, and state the limits of that evidence.
- Trace the failure back to the component that introduces it. Check inputs and outputs at boundaries and use the smallest check that can distinguish plausible causes. Revisit the hypothesis when a fix fails.
- Fix the cause and verify the original failure against the final change. Add a focused regression test if existing coverage would miss the failure and the test can reproduce it reliably.
For urgent containment, use a reversible mitigation within the authorized scope. State what it contains and which cause remains unconfirmed.