“debugging”

Systematically debug an error or unexpected behavior.

Systematic debugging workflow for isolating and fixing bugs

Use when the user says 'diagnose', 'debug this', reports something broken/throwing/failing/slow, when encountering a bug/test failure/unexpected behavior and…

Debug issues systematically.

Compatibility route to the author's complete Superpowers systematic-debugging skill for failures and root-cause investigation.

Structured debugging protocol.

Systematic bug investigation with hypothesis tracking

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

Use when something is failing, regressing, or behaving unexpectedly and the goal is root-cause analysis, narrowest fix, and verification.

Systematic root-cause isolation and minimal fix proposal for software bugs.

Use for runtime bugs: crashes, wrong output, intermittent or silent failures, flaky tests, code that works locally but not in prod.

Systematic debugging workflow using Approved Logs pattern.

When to use this skill for systematic debugging including root cause analysis, error tracing, performance profiling, and memory leak detection

Systematic debugging with diagnostic paths covering data processing, rendering, state machine, asset loading, form/input, and build issues

When there is a bug, error, failed test, regression, performance drop, unexpected result, or anomalous data, establish a tight feedback loop and find the root…

Find the root cause of a defect or a symptom by first building a feedback loop that shows the failure on demand, recording the behaviour that must not change…

Diagnose failures from evidence and make the smallest safe correction.

Use when diagnosing a failure, crash, regression, or wrong result before fixing.

Diagnose failures from evidence before changing code.

Systematically track down a bug.

Reproduce a failure, isolate the cause, and keep the fix bounded.

Diagnose defects systematically by reproducing the issue, isolating the failing layer, testing hypotheses, fixing root cause, and adding regression protection.

系统调试：遇到 bug、报错、测试失败、性能退化、意外实验结果或异常数据时，先于任何修复动作使用；仅背景不清而无故障信号时用 grounding，正常执行既定计划时用 executing-plans。

Structured root-cause investigation for bugs and failures.