Skills systematic-debugging
📦

systematic-debugging

v1.0 Content revision r1 Safe ⚙️ External commands

Debug Software Issues Systematically

Debugging often fails when fixes start before evidence is understood. This skill guides Claude, Codex, and Claude Code through root cause analysis, pattern comparison, hypothesis testing, and verified repair.

Supports: Claude Codex Code(CC)
🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "systematic-debugging" from https://skillstore.io/skills/doyajin174-systematic-debugging.md and its manifest at https://skillstore.io/api/skills/doyajin174-systematic-debugging/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/doyajin174-systematic-debugging.md Signed manifest GET /api/skills/doyajin174-systematic-debugging/manifest Signed lockfile GET /api/skills/doyajin174-systematic-debugging/lockfile

Test it

Using "systematic-debugging". A test started failing after a refactor.

Expected outcome:

The assistant records the exact error, reproduces the failure, checks the refactor, compares a passing path, and tests one hypothesis.

Using "systematic-debugging". A production workflow returns unexpected data.

Expected outcome:

The assistant traces data backward from the bad output, identifies the first divergence, and verifies the fix with a focused check.

Using "systematic-debugging". Three attempted fixes did not solve the bug.

Expected outcome:

The assistant stops the repair loop, summarizes failed hypotheses, and recommends reviewing design assumptions before further edits.

Security Audit

Safe
v8 • 7/6/2026 Open versioned report

All external command findings are false positives caused by Markdown fence delimiters around non-executable debugging guidance. The high entropy heuristic is also a false positive because the file is readable Markdown with Korean text and symbols, and no prompt injection or malicious intent was found.

1
Files scanned
126
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (13)
SKILL.md:23-29 SKILL.md:29-33 SKILL.md:33-38 SKILL.md:38-42 SKILL.md:42-51 SKILL.md:51-55 SKILL.md:55-61 SKILL.md:61-73 SKILL.md:73-78 SKILL.md:78-82 SKILL.md:82-109 SKILL.md:109-113 SKILL.md:113-118
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/doyajin174-systematic-debugging/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/doyajin174-systematic-debugging/security.svg)](https://skillstore.io/skills/doyajin174-systematic-debugging?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/doyajin174-systematic-debugging?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/doyajin174-systematic-debugging/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/doyajin174-systematic-debugging.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

Doyajin174. (2026). systematic-debugging security audit report (audit version 8) [Author version 1.0]. Skillstore. https://skillstore.io/skills/doyajin174-systematic-debugging/audits/8

BibTeX citation

@techreport{doyajin174-doyajin174-systematic-debugging-2026, author = {Doyajin174}, title = {systematic-debugging security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/doyajin174-systematic-debugging/audits/8}, note = {Author version 1.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "systematic-debugging security audit report (audit version 8)" version: "1.0" type: report authors: - name: "Doyajin174" date-released: "2026-07-06" url: "https://skillstore.io/skills/doyajin174-systematic-debugging/audits/8" identifiers: - type: other value: "skillstore:doyajin174-systematic-debugging:audit:8" description: "Skillstore immutable audit report identifier"

Compare variants

12 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
Asmayaseen Recommended

asmayaseen-systematic-debugging

Skillstore Score 81
Evidence Confidence High
Skillstore usage 20
Updated

2026-08-21

ChrisWiles

chriswiles-systematic-debugging

Skillstore Score 79
Evidence Confidence High
Skillstore usage 11
Updated

2026-08-21

Doyajin174 Current

doyajin174-systematic-debugging

Skillstore Score 79
Evidence Confidence High
Skillstore usage 9
Updated

2026-08-21

DMJGilbert

dmjgilbert-systematic-debugging

Skillstore Score 79
Evidence Confidence High
Skillstore usage 9
Updated

2026-08-21

CodingCossack

codingcossack-systematic-debugging

Skillstore Score 74
Evidence Confidence High
Skillstore usage 59
Updated

2026-08-21

ZhanlinCui

zhanlincui-systematic-debugging

Skillstore Score 71
Evidence Confidence High
Skillstore usage 90
Updated

2026-08-21

obra

obra-systematic-debugging

Skillstore Score 71
Evidence Confidence High
Skillstore usage 14
Updated

2026-08-21

Cycleaddict

cycleaddict-systematic-debugging

Skillstore Score 71
Evidence Confidence High
Skillstore usage 5
Updated

2026-08-21

davila7

davila7-systematic-debugging

Skillstore Score 70
Evidence Confidence High
Skillstore usage 5
Updated

2026-08-21

DYAI2025

dyai2025-systematic-debugging

Skillstore Score 70
Evidence Confidence Medium
Skillstore usage 45
Updated

2026-08-21

Cygnusfear

cygnusfear-systematic-debugging

Skillstore Score 50
Evidence Confidence High
Skillstore usage 5
Updated

2026-08-21

sickn33

sickn33-systematic-debugging

Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 12
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
71
Community
91
Spec Compliance

What You Can Build

Investigate failing tests

Use the four-phase flow to reproduce failures, compare passing cases, and verify a single fix.

Document bug triage

Create a clear record of symptoms, evidence, hypotheses, tests, and repair results.

Control AI coding work

Require Claude, Codex, or Claude Code to explain evidence before editing code.

Try These Prompts

Start a bug investigation 
Use systematic debugging on this issue. First restate the symptom, then list the evidence you need before proposing any fix.
Analyze a failing test 
Apply the four debugging phases to this failing test. Identify the exact failure, reproduction steps, recent changes, and one first hypothesis.
Compare working and broken behavior 
Find a working example that should behave like this broken case. Compare inputs, dependencies, configuration, and data flow before suggesting a fix.
Run a controlled repair loop 
Manage this debugging session with one hypothesis, one minimal test, and one fix per cycle. Stop after three failed attempts and reassess architecture.

Best Practices

  • Capture the exact error message and reproduction path before changing code.
  • Change one variable at a time and record the result.
  • Keep rollback options available before applying a fix.

Avoid

  • Do not patch symptoms before identifying the root cause.
  • Do not combine multiple speculative fixes in one change.
  • Do not continue the same approach after repeated failed attempts.

Frequently Asked Questions

What does this skill help with?
It helps debug bugs, failed tests, and unexpected behavior through a structured root cause workflow.
Does it run commands automatically?
No. It describes a debugging process and relies on the assistant or user to choose approved diagnostic actions.
Can it fix every bug?
No. It improves investigation discipline, but results depend on evidence, system complexity, and available tests.
Who should use it?
Developers, QA engineers, and AI coding assistant users can use it to avoid speculative fixes.
How is it different from normal debugging?
It enforces phases, evidence collection, hypothesis testing, and stopping rules before implementation.
Is it useful with Claude Code or Codex?
Yes. It gives Claude Code and Codex a clear process for investigation before code edits.

Developer Details

Author

Doyajin174

License

MIT

Author version

v1.0

Skillstore revision

r1

Version notice

The author-declared version is not valid SemVer.

Repository

https://github.com/Doyajin174/myskills/tree/main/.public/skills/systematic-debugging

Ref

72d5025b022c77f7a51bdf5c1637c689c80e89d1

Maintenance freshness

7/18/2026

Usage

7 downloads · 299 views

File structure

📄 SKILL.md