Systematic Debugging

What it does

This skill organizes debugging around evidence collection and a testable explanation of the failure. It asks the agent to establish a reproducible case, inspect relevant changes and trace the boundary where expected behavior diverges from observed behavior. The useful output is a diagnosis supported by observations and a focused correction, rather than a growing collection of speculative edits.

Best for

Developers handling reproducible defects across application layers, especially when several earlier fixes changed symptoms without explaining the cause. It can also help organize a handoff because the investigation leaves a record of observations, rejected explanations and the remaining uncertainty.

Tradeoffs and requirements

The workflow can take longer than an immediate guess. That investment is worthwhile for recurring or consequential failures, while tiny disposable experiments may need a shorter investigation. The skill cannot make incomplete logs, unreliable test environments or missing production access disappear. Commands and data access still require the permissions appropriate to the environment.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code; this catalog never runs it.

npx skills add https://github.com/obra/superpowers/tree/2ce8aa15d05bd57213e6f746f953aafb7ded7a8b/skills/systematic-debugging --skill systematic-debugging

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Shell Or Package Install — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

88/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

99/100

99

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Capture the exact trigger and expected behavior, reproduce it with the smallest useful input, identify which component first behaves incorrectly, then change one relevant variable. Pair it with test-driven-development for a regression case and verification-before-completion for the final evidence check.

How to judge the result

A reviewer should be able to reproduce the original failure, see why the proposed cause explains it, and observe the same test pass after the correction. Record any behavior that remains untested.