Back to catalog
Human reviewedDevelopment

Skill dossier

systematic-debugging

Source declaration

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

The author's original description, preserved in English. It describes intent, not verified performance.

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

developmentscripts

Research summary

Human reviewed

Skill Atlas editorial baseline · editorial-0.1.0

A diagnostic workflow Skill that insists on understanding root cause before changing code. It emphasizes evidence, hypotheses and validation instead of speculative fixes.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Structures debugging as evidence gathering and hypothesis testing.
  • Discourages random changes and premature fixes.
  • Requires verification after a proposed correction.

Limitations & scope

  • Cannot replace domain knowledge or missing observability.
  • May be slower than a known one-line fix.
  • No empirical success rate is recorded.

Relevant for

  • Developers handling non-trivial bugs
  • On-call engineers
  • Agents that patch symptoms

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
4
scripts
2
references
3
Size
28.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/systematic-debugging/condition-based-waiting-example.tsScript4.9 KB
skills/systematic-debugging/condition-based-waiting.mdReference3.4 KB
skills/systematic-debugging/defense-in-depth.mdReference3.6 KB
skills/systematic-debugging/find-polluter.shScript1.9 KB
skills/systematic-debugging/root-cause-tracing.mdReference5.2 KB
skills/systematic-debugging/SKILL.mdInstruction9.3 KB

SKILL.md frontmatter

{
  "name": "systematic-debugging",
  "description": "Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes"
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Confirm scope

    Read the trigger conditions and decide whether this skill matches the current task.

  2. 02
    Action

    Load instructions

    Claude Code reads the full SKILL.md when the skill is selected.

  3. 03
    Decision

    Use resources deliberately

    Read references or run scripts only when the documented workflow requires them.

  4. 04
    Output

    Deliver and verify

    Produce the requested artifact and verify it against the source-described acceptance criteria.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

52 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessNot observed
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

52 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 52 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Review any diagnostics scripts before granting broad filesystem or network access.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/obra/superpowers.git cd superpowers # Copy this skill directory into one of: # ~/.claude/skills/systematic-debugging # .claude/skills/systematic-debugging
  1. Open the immutable source at https://github.com/obra/superpowers/tree/22f0b463e7a5e579904dd6211a520321035526f7/skills/systematic-debugging/SKILL.md.
  2. Review the license, prerequisites and all bundled resources.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Check that SKILL.md is discoverable at the destination, then ask Claude Code to use the named skill on a test task.

Prerequisites

  • Cannot replace domain knowledge or missing observability.
  • May be slower than a known one-line fix.
  • No empirical success rate is recorded.

Example prompts

Representative task

Use the systematic-debugging skill to help with this task. First summarize what the skill will do, then execute its documented workflow and show the source-linked evidence for each major decision.

Inspect before use

Read the systematic-debugging skill files at https://github.com/obra/superpowers/tree/22f0b463e7a5e579904dd6211a520321035526f7/skills/systematic-debugging/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Strong process discipline for hard bugs.
  • Keeps diagnosis and repair separate.

Considerations

  • Overhead on obvious failures.
  • Depends on available logs and reproduction steps.
Research conclusion

Recommended as a reasoning framework for difficult defects, not as a replacement for tests or observability.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

obrasuperpowersskills/systematic-debugging
Source type
Community
Commit
22f0b463e7a5e579904dd6211a520321035526f7
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
322,183
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.