Skills systematic-debugging

📦

systematic-debugging

Name: systematic-debugging
Author: Cycleaddict

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

Debug Bugs Systematically

Bugs waste time when teams guess at fixes before proving the cause. This skill guides Claude, Codex, and Claude Code through evidence-based debugging.

Supports: Claude Codex Code(CC)

📊 71 Adequate

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

Test it

Using "systematic-debugging". A payment test expects completed status but receives pending status.

Expected outcome:

The response first lists the observable failure, recent changes, and a reproduction plan. It then states one hypothesis and one minimal test.

Using "systematic-debugging". A flaky async test uses a fixed delay before checking results.

Expected outcome:

The response recommends waiting for the actual event or state change, adds a clear timeout, and verifies the failure disappears.

Using "systematic-debugging". A Git command runs in the wrong directory during tests.

Expected outcome:

The response traces the empty directory value back through callers and proposes validation at each layer.

Security Audit

Medium Risk

v8 • 7/5/2026 Open versioned report

Most static findings are false positives caused by Markdown fences, TypeScript template literals, ordinary examples, and safe NODE_ENV checks. One medium issue remains: a diagnostic Bash example may print environment and signing identity details to logs. No prompt injection, malware intent, network exfiltration, or hidden execution was found.

Files scanned

1,262

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Medium

SKILL.md:90-105

Diagnostic Logging May Expose Environment Data

SKILL.md instructs users to print secret availability, environment variables matching IDENTITY, keychain state, and signing identity details. This is diagnostic rather than exfiltration, but it can disclose sensitive CI or signing metadata in shared logs.

The cited Bash snippet explicitly prints environment and keychain information. No network transmission is present, so the risk is log exposure rather than direct exfiltration.

Capability review items (1)

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

SKILL.md:90-106

Ruby/shell backtick execution

```bash

This Bash example tells users to run local commands that print environment and keychain signing state. The intent is diagnostic, but these outputs can expose sensitive CI or signing metadata in logs.

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/cycleaddict-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/cycleaddict-systematic-debugging/security.svg)](https://skillstore.io/skills/cycleaddict-systematic-debugging?utm_source=security_passport_badge)

HTML badge

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

Embed card

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

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

BibTeX citation

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

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 Current

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

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Investigate Recurring Bugs

Trace a failure from symptom to original trigger before changing code.

Stabilize Flaky Tests

Replace timing guesses with condition-based waiting and clear verification.

Guide AI Coding Sessions

Keep Claude, Codex, or Claude Code from proposing fixes before evidence is gathered.

Try These Prompts

Start a Bug Investigation

Use systematic debugging for this bug. First list the observed failure, reproduction steps, recent changes, and missing evidence before suggesting any fix.

Trace a Failing Test

A test is failing. Use the skill to trace the failure backward through callers, identify where bad data enters, and state one hypothesis.

Compare Broken and Working Paths

Find a working example of the same pattern, compare it with the broken path, and list differences before proposing a minimal test.

Audit a Failed Debugging Session

Several fixes have failed. Review the evidence, identify untested assumptions, decide whether the architecture should be questioned, and propose next steps.

Best Practices

Capture the error, reproduction steps, and recent changes before proposing any fix.
Test one hypothesis at a time with the smallest useful change.
Add a failing test or clear reproduction before changing production code.