Skills systematic-debugging

📦

systematic-debugging

Name: systematic-debugging
Author: sickn33

Content revision r1 High Risk ⚙️ External commands📁 Filesystem access🔑 Env variables

Debug Software Issues Systematically

Random fixes waste time and create regressions. This skill guides Claude, Codex, and Claude Code through root-cause debugging before implementation.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

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. Stop and obtain explicit user consent before installing or changing files.

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". A payment test sometimes returns pending status instead of completed status.

Expected outcome:

The skill would ask for reproduction steps, recent changes, event timing evidence, and the first point where status stops updating.

Using "systematic-debugging". A git operation runs in the wrong directory during tests.

Expected outcome:

The skill would trace the directory value back through callers, identify the source of the empty path, and add validation at several layers.

Using "systematic-debugging". Three attempted fixes changed different parts of a shared workflow and still failed.

Expected outcome:

The skill would stop more patching, summarize failed hypotheses, and evaluate whether the architecture is the actual problem.

Security Audit

High Risk

v4 • 7/7/2026 Open versioned report

Most static findings are false positives from markdown fences, JavaScript template literals, and documentation examples. Real risk remains in the main guidance for printing environment and signing diagnostics, plus the bundled shell script that executes npm tests. No prompt-injection attempt, malicious persistence, or data-exfiltration code was found.

Files scanned

1,262

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

High

SKILL.md:90-105

Sensitive Diagnostic Logging Guidance

The main skill suggests debugging commands such as env grep for IDENTITY and keychain identity listing. In CI or shared logs, this can expose secret values or signing metadata.

The guidance appears in the primary skill instructions and targets secrets, environment propagation, and signing state. The commands are examples, but users may copy them into CI logs.

Medium

find-polluter.sh:21-42

Bundled Test Runner Executes Project Code

The find-polluter helper discovers test files and runs npm test for each match. Running this in an untrusted repository can execute arbitrary package scripts while suppressing output.

The executable shell script directly invokes npm test on discovered paths. This is expected debugging behavior, but it creates a real execution risk in untrusted projects.

Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium

find-polluter.sh:22

Shell command substitution

TEST_FILES=$(find . -path "$TEST_PATTERN" | sort)

This bundled shell script runs find and sort over the current project using a caller-supplied path pattern. Arguments are quoted, but it is real external command execution in marketplace content.

Medium

find-polluter.sh:23

Shell command substitution

TOTAL=$(echo "$TEST_FILES" | wc -l | tr -d ' ')

The script executes echo, wc, and tr inside command substitution while processing discovered file paths. The use is benign counting logic, but it is active shell execution in a user-runnable script.

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

Copy report link

https://skillstore.io/skills/sickn33-systematic-debugging/audits/4?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 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-systematic-debugging/audits/4

BibTeX citation

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

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

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

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 Current

sickn33-systematic-debugging

Skillstore Score 38

Evidence Confidence Medium

Skillstore usage 12

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Diagnose Failing Tests

Use the process to reproduce a failure, inspect recent changes, and confirm one root-cause hypothesis before editing code.

Stabilize Flaky Async Tests

Replace timing guesses with condition-based waiting patterns and clear timeout messages.

Review Repeated Failed Fixes

Pause after multiple failed fixes, reassess architecture, and avoid stacking unrelated changes.

Try These Prompts

Investigate a Test Failure

Use systematic debugging on this failing test: [test name]. Error: [message]. Start with evidence gathering and do not propose fixes yet.

Trace Bad Data

Trace this bad value backward through the call stack: [value and symptom]. Identify where it first becomes wrong before suggesting changes.

Stabilize a Flaky Test

This test uses sleeps and fails intermittently: [summary]. Find the real condition to wait for and propose a minimal verification plan.

Reassess Failed Fixes

I tried these fixes and they failed: [list]. Apply the systematic process, question the architecture if needed, and define the next experiment.

Best Practices

Reproduce the problem and read the full error before proposing any fix.
Test one clear hypothesis at a time with the smallest useful change.
Create a failing test or repeatable check before implementing the final fix.

Avoid

Guessing a quick fix before finding the root cause.
Bundling several unrelated changes into one debugging attempt.
Fixing the deepest symptom without tracing where the bad input began.

Frequently Asked Questions

When should I use this skill?

Use it when a bug, test failure, flaky test, build failure, or unexpected behavior needs investigation before code changes.

Does it write the fix for me?

It guides the investigation first. After the root cause is clear, it supports a minimal fix and verification plan.

Can it help under time pressure?

Yes. The process is designed to reduce wasted fixes when fast guesses feel tempting.

Does it require a specific language?

No. The workflow applies broadly, though examples use TypeScript, shell, and common test tooling.

Is the included script safe to run?

Run it only in trusted repositories. It executes local npm tests and can trigger package scripts.

How does it handle flaky tests?

It encourages waiting for real conditions, adding clear timeouts, and documenting any timing-based waits that remain.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

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

Ref

9f814fc6a43fd99946f2da5e0df231c65a38bc76

Maintenance freshness

7/18/2026

Usage

10 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

systematic-debugging

Install with my Agent

Agent-readable resources

Test it

Security Audit

Confirmed security concerns (2)

Risk Factors

Copy report link

Markdown badge

HTML badge

Embed card

APA citation

BibTeX citation

CITATION.cff

Compare variants

Skillstore Score

What You Can Build

Diagnose Failing Tests

Stabilize Flaky Async Tests

Review Repeated Failed Fixes

Try These Prompts

Best Practices

Avoid

Frequently Asked Questions

Developer Details