Skills systematic-debugging
📦

systematic-debugging

Content revision r2 Safe ⚙️ External commands

Debug Technical Failures Systematically

Quick fixes often hide the real cause and create regressions. This skill structures investigation, hypothesis testing, implementation, and verification around collected evidence.

Supports: Claude Codex Code(CC)
🥈 81 Silver

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/asmayaseen-systematic-debugging.md and its manifest at https://skillstore.io/api/skills/asmayaseen-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/asmayaseen-systematic-debugging.md Signed manifest GET /api/skills/asmayaseen-systematic-debugging/manifest Signed lockfile GET /api/skills/asmayaseen-systematic-debugging/lockfile

Test it

Using "systematic-debugging". A unit test fails because a project directory is empty.

Expected outcome:

  • Observed symptom: initialization runs in the current directory.
  • Root-cause hypothesis: setup data is read before initialization.
  • Verification: inspect the first assignment and reproduce with one focused test.

Using "systematic-debugging". A continuous integration job fails between build and signing.

Expected outcome:

  • Capture the artifact name and checksum after the build.
  • Capture the received path and configuration before signing.
  • Compare both boundaries in one failing run.

Using "systematic-debugging". Three attempted fixes reveal new shared-state failures.

Expected outcome:

Stop applying patches. Document the coupling revealed by each attempt and discuss the architecture before making another change.

Security Audit

Safe
v9 • 7/23/2026 Open versioned report

All 14 static findings are false positives. The command patterns are inert documentation examples, Markdown delimiters, or inline code, with no automatic execution or malicious intent.

3
Files scanned
346
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (11)
references/root-cause-tracing.md:67 references/root-cause-tracing.md:78 SKILL.md:19-21 SKILL.md:21-52 SKILL.md:52-60 SKILL.md:60-125 SKILL.md:125-136 SKILL.md:136-144 SKILL.md:144-147 SKILL.md:147-156 SKILL.md:156-174
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/asmayaseen-systematic-debugging/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/asmayaseen-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

Asmayaseen. (2026). systematic-debugging security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/asmayaseen-systematic-debugging/audits/9

BibTeX citation

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

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 9)" version: "unspecified" type: report authors: - name: "Asmayaseen" date-released: "2026-07-23" url: "https://skillstore.io/skills/asmayaseen-systematic-debugging/audits/9" identifiers: - type: other value: "skillstore:asmayaseen-systematic-debugging:audit:9" 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 Current

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

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 8
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
64
Architecture
85
Maintainability
87
Content
72
Community
91
Spec Compliance

What You Can Build

Diagnose Application Bugs

Trace unexpected application behavior to its source before changing production code.

Stabilize Failing Tests

Separate timing symptoms, polluted state, and invalid setup data through focused experiments.

Investigate Pipeline Failures

Instrument component boundaries to locate where data or configuration first becomes incorrect.

Try These Prompts

Investigate a Test Failure 
Analyze this failing test systematically. Identify missing evidence, state one root-cause hypothesis, and propose the smallest verification step: [failure details]
Trace an Invalid Value 
Trace this invalid value backward through the call chain. Identify its earliest source and distinguish the root cause from downstream symptoms: [trace details]
Isolate a Component Failure 
Design minimal instrumentation for each component boundary. Specify inputs, outputs, configuration checks, and one run that will locate the failing component: [system details]
Reassess Repeated Fix Failures 
Review these failed fixes for shared state or coupling. Decide whether another hypothesis is justified or an architectural discussion is required: [attempt history]

Best Practices

  • Collect reproducible evidence before proposing a fix.
  • Change one variable at a time and record the result.
  • Add a failing test, fix the source, and check for regressions.

Avoid

  • Do not stack several speculative fixes into one test run.
  • Do not patch the visible symptom without tracing its input.
  • Do not continue repeated fixes when evidence indicates architectural coupling.

Frequently Asked Questions

When should I use this skill?
Use it for bugs, test failures, and unexpected behavior that require evidence-based diagnosis before implementation.
Can it debug any programming language?
Yes. The method is language independent, but diagnostics still depend on the available tools and project context.
Does it apply fixes automatically?
It guides a focused fix after root-cause investigation. Actual changes depend on the agent, permissions, and user request.
What information should I provide?
Provide the error, stack trace, reproduction steps, recent changes, expected behavior, and relevant logs.
How does it handle flaky tests?
It recommends waiting for observable conditions and isolating the test that first pollutes shared state.
What happens after several fixes fail?
After three failed focused fixes, it recommends stopping and discussing possible architectural coupling before continuing.

Developer Details

Author

Asmayaseen

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/Asmayaseen/hackathon-2/tree/main/.claude/skills/systematic-debugging

Ref

89edfdc710d0846129dcee6a929477b04f08052c

Maintenance freshness

7/24/2026

Usage

13 downloads · 303 views

File structure

📁 references/

📄 root-cause-tracing.md

📁 scripts/

📄 verify.py

📄 SKILL.md