Skills systematic-debugging
📦

systematic-debugging

Content revision r2 Safe ⚙️ External commands📁 Filesystem access🔑 Env variables

Debug Software Systematically

Guessing at fixes wastes time and can hide the real defect. This skill guides evidence gathering, root-cause analysis, focused testing, and verified implementation.

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

Test it

Using "systematic-debugging". The payment test sometimes remains pending after a fixed two-second sleep.

Expected outcome:

Observed symptom: status remains pending intermittently. Replace the fixed delay with a bounded wait for the completion event, then trace missing events before changing production logic.

Using "systematic-debugging". A command creates repository data in the source directory during tests.

Expected outcome:

  • Immediate cause: the command receives an empty working directory.
  • Tracing target: find where the empty value first enters the call chain.
  • Confirmation: reproduce with one focused test before changing validation.
  • Repair: fix the source and add checks at each relevant boundary.

Using "systematic-debugging". A local build works, but CI reports a missing signing identity.

Expected outcome:

Record configuration presence at each authorized boundary without values. Compare propagation between local and CI environments, test one forwarding hypothesis, then verify the built artifact.

Security Audit

Safe
v5 • 9/6/2026 Open versioned report

All 38 static findings are false positives caused by TypeScript template literals, Markdown formatting, benign prose, or non-sensitive NODE_ENV checks. The diagnostic helper runs a fixed npm test command without a shell and includes isolation guidance and input constraints.

11
Files scanned
1,311
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (19)
condition-based-waiting-example.ts:36 condition-based-waiting-example.ts:79 condition-based-waiting-example.ts:128 condition-based-waiting.md:75-81 defense-in-depth.md:31-34 defense-in-depth.md:34-38 defense-in-depth.md:64-66 defense-in-depth.md:66-72 find-polluter.sh:56 SKILL.md:21-23 SKILL.md:23-79 SKILL.md:79-89 SKILL.md:89-92 SKILL.md:92-102 SKILL.md:102-110 SKILL.md:110-175 SKILL.md:175-278 SKILL.md:278-279 SKILL.md:279-280
📁 Filesystem access (2)
condition-based-waiting.md:55 CREATION-LOG.md:10
🔑 Env variables (4)
defense-in-depth.md:58 defense-in-depth.md:58 root-cause-tracing.md:77 root-cause-tracing.md:77
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/sickn33-systematic-debugging/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

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

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

BibTeX citation

@techreport{sickn33-sickn33-systematic-debugging-2026, author = {sickn33}, title = {systematic-debugging security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-systematic-debugging/audits/5}, 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 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-09-06" url: "https://skillstore.io/skills/sickn33-systematic-debugging/audits/5" identifiers: - type: other value: "skillstore:sickn33-systematic-debugging:audit:5" 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 22
Updated

2026-09-09

sickn33 Current

sickn33-systematic-debugging

Skillstore Score 79
Evidence Confidence High
Skillstore usage 16
Updated

2026-09-09

ChrisWiles

chriswiles-systematic-debugging

Skillstore Score 79
Evidence Confidence High
Skillstore usage 13
Updated

2026-09-09

DMJGilbert

dmjgilbert-systematic-debugging

Skillstore Score 79
Evidence Confidence High
Skillstore usage 11
Updated

2026-09-09

Doyajin174

doyajin174-systematic-debugging

Skillstore Score 79
Evidence Confidence High
Skillstore usage 10
Updated

2026-09-09

CodingCossack

codingcossack-systematic-debugging

Skillstore Score 74
Evidence Confidence High
Skillstore usage 62
Updated

2026-09-09

ZhanlinCui

zhanlincui-systematic-debugging

Skillstore Score 71
Evidence Confidence High
Skillstore usage 92
Updated

2026-09-09

obra

obra-systematic-debugging

Skillstore Score 71
Evidence Confidence High
Skillstore usage 16
Updated

2026-09-09

Cycleaddict

cycleaddict-systematic-debugging

Skillstore Score 71
Evidence Confidence High
Skillstore usage 7
Updated

2026-09-09

davila7

davila7-systematic-debugging

Skillstore Score 70
Evidence Confidence High
Skillstore usage 8
Updated

2026-09-09

DYAI2025

dyai2025-systematic-debugging

Skillstore Score 70
Evidence Confidence Medium
Skillstore usage 47
Updated

2026-09-09

Cygnusfear

cygnusfear-systematic-debugging

Skillstore Score 50
Evidence Confidence High
Skillstore usage 7
Updated

2026-09-09

Skillstore Score

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

What You Can Build

Diagnose a failing feature

Trace a reproducible application failure, compare working paths, test one hypothesis, and implement a regression-covered repair.

Stabilize asynchronous tests

Replace guessed delays with bounded waits for observable events, state, counts, or files.

Investigate production incidents

Separate authorized containment from root-cause work while preserving evidence and redacting sensitive diagnostic data.

Try These Prompts

Investigate a simple failure 
Use systematic debugging for this failure: [error]. Start with reproduction steps and evidence. Do not propose a fix until you identify a likely cause.
Compare working and failing paths 
Analyze [failing path] against [working path]. List relevant differences, recent changes, dependencies, and one testable root-cause hypothesis.
Trace a deep failure 
Trace [symptom] backward through the call and data flow. Identify the earliest invalid state, supporting evidence, and a minimal confirmation test.
Design a verified repair 
Given this confirmed cause: [cause], design one focused fix, a failing regression test, layered validation, and verification steps. State remaining uncertainty.

Best Practices

  • Capture the smallest useful evidence set and redact secrets before sharing logs.
  • Change one variable per hypothesis so each result can confirm or reject a specific cause.
  • Add a focused regression test and rerun relevant verification before claiming resolution.

Avoid

  • Do not stack speculative fixes without returning to evidence after a failed hypothesis.
  • Do not use arbitrary delays when an observable completion condition is available.
  • Do not dump environment variables, credentials, private payloads, or unnecessary personal paths into diagnostics.

Frequently Asked Questions

When should I use this skill?
Use it for reproducible bugs, test failures, build problems, integration errors, performance issues, and unexpected behavior.
Can I contain a production incident before finding the root cause?
Yes. Apply an authorized rollback or containment action, label it as temporary, preserve evidence, and continue root-cause analysis.
What information should I provide?
Provide the exact error, reproduction steps, revision, runtime, recent changes, observed evidence, and relevant working examples.
Does the skill execute commands automatically?
No. It provides examples and a helper script that runs only when explicitly invoked.
Is the polluter helper safe for any repository?
No. It executes selected project tests, so use an isolated checkout and verify that the test runner accepts file arguments.
What happens after three failed fixes?
Stop adding fixes, reassess assumptions and coupling, and discuss whether the architecture or debugging model needs revision.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/systematic-debugging

Ref

ae6ba0f1a47f0b4427a656b2202f2ff34bfea6be

Maintenance freshness

9/6/2026

Usage

12 downloads · 181 views

File structure

📄 condition-based-waiting-example.ts

📄 condition-based-waiting.md

📄 CREATION-LOG.md

📄 defense-in-depth.md

📄 find-polluter.sh

📄 root-cause-tracing.md

📄 SKILL.md

📄 test-academic.md

📄 test-pressure-1.md

📄 test-pressure-2.md

📄 test-pressure-3.md

More from sickn33

View all

Related Skills

View all