Systematic Debugging

用于根因诊断:当 bug、测试失败或异常行为需要先做 root-cause analysis,再决定怎么修时使用。Prefer `test-driven-development` when 修复路径已清晰到可以先写 failing test,Prefer `verification-before-completion` when 实现已完成、准备宣称成功。

hebertzhu 08a4c64 1.2 KB Updated

File contents

systematic-debugging

Intent

  • 用于根因诊断:当 bug、测试失败或异常行为需要先做 root-cause analysis,再决定怎么修时使用。Prefer test-driven-development when 修复路径已清晰到可以先写 failing test,Prefer verification-before-completion when 实现已完成、准备宣称成功。

Default operating pattern

  1. Capture the actual engineering goal and the next decision that matters.
  2. Inspect the current code, tests, branch state, or CI context before acting.
  3. Take the smallest next action that reduces uncertainty or advances delivery.
  4. Collect fresh evidence before claiming progress.
  5. Summarize status, risks, and the next recommended step.

Pack fit

  • Included in: engineering-workflow, release-quality
  • Keep examples generic, privacy-safe, and portable across hosts.

Boundary

  • Do not use only to rubber-stamp a fix that is already implemented.

hebertzhu/agent-foundry/tree/main/skills/systematic-debugging commit 08a4c64132

Frequently asked questions

npx skillmds@latest add hebertzhu/systematic-debugging